<div dir="ltr">I used <font face="courier new, monospace">xxd</font>, <font face="courier new, monospace">cut</font> and <font face="courier new, monospace">meld</font> to compare and analyze the three dumps. Results:<div>
<br><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div><font face="courier new, monospace">Yaesu FTM-400D</font></div></div><div><div><font face="courier new, monospace"><br></font></div>
</div><div><div><font face="courier new, monospace">Comparison of memory dumps to SD card, CLN (assumed to be full memory dump),</font></div></div><div><div><font face="courier new, monospace">MEM (memory/channel settings) and SYS (system settings).</font></div>
</div><div><div><font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">Johan Adler, 2014-03-10 (March 10, 2014)</font></div></div><div><div><font face="courier new, monospace"><br>
</font></div></div><div><div><font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x0000 to 0x007f: Unknown, identical in all dumps</font></div></div><div><div><font face="courier new, monospace">0x0080 to 0x017f: Settings</font></div>
</div><div><div><font face="courier new, monospace">0x0180 to 0x01ff: Present in both settings (same address) and memories (at 0x0080 to 0x00ff).</font></div></div><div><div><font face="courier new, monospace">0x0200 to 0x027f: Memories (0x0100 to 0x017f)</font></div>
</div><div><div><font face="courier new, monospace">0x0280 to 0x02ff: Settings (0x0200 to 0x027f)</font></div></div><div><div><font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x0300 to 0x03ff: Unknown, 0xff in my dump.</font></div>
</div><div><div><font face="courier new, monospace">0x0400 to 0x047f: Contains data, APRS-related settings?</font></div></div><div><div><font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x0480 to 0x04ff: Memories (0x0180 to 0x01ff)</font></div>
</div><div><div><font face="courier new, monospace">0x0500 to 0x057f: Settings (0x0280 to 0x02ff)</font></div></div><div><div><font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x0580 to 0x05ff: Unknown, 0xca and 0xff in my dump.</font></div>
</div><div><div><font face="courier new, monospace">0x0600 to 0x067f: Contains data, likely APRS-related.</font></div></div><div><div><font face="courier new, monospace">0x0680 to 0x07ff: Unknown, 0xca in my dump.</font></div>
</div><div><div><font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x0800 to 0x69ff: Memories (0x0200 to 0x63ff), I guess the two main banks.</font></div></div><div><div>
<font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x7800 to 0x780f: Unknown, 'ALL' padded with ASCII space in my dump. APRS-related?</font></div></div><div><div>
<font face="courier new, monospace"><br></font></div></div><div><div><font face="courier new, monospace">0x7c00 to 0x7dff: Unknown, looks like data, maybe settings.</font></div></div><div><div><font face="courier new, monospace"><br>
</font></div></div><div><div><font face="courier new, monospace">0x8000 to 0x????: APRS reports/contacts, full messages received, 0x80 bytes each.</font></div></div><div><div><font face="courier new, monospace"><br></font></div>
</div><div><div><font face="courier new, monospace">0xe400 to 0x????: APRS contacts, 0x20 bytes each.</font></div></div></blockquote><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div style="text-align:left">
<br></div><div style="text-align:left"><br></div><div style="text-align:center"><img src="https://lh3.googleusercontent.com/_b-IGKDHEVWw/TaWhfQWMrII/AAAAAAAADsc/264AZ2BJtVk/R0011581-3-new-bw-3-256px.png" width="96" height="93"></div>
</div>
<br><br><div class="gmail_quote">On Mon, Mar 10, 2014 at 7:06 AM, Johan Adler <span dir="ltr"><<a href="mailto:johan.adler@gmail.com" target="_blank">johan.adler@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The radio can save different backups to the card, either a full memory<br>
dump (76800 bytes, 0c12c00), only the settings (1024 bytes, 0x400), or<br>
only the memories (25600 bytes, 0x6400).<br>
<br>
Filenames and paths, relative to SD card root:<br>
<br>
Full memory dump ("clone"): FTM400D/BACKUP/CLONE/CLNFTM400D.dat<br>
Memories (channel data, I presume): FTM400D/BACKUP/MEMORY/MEMFTM400D.dat<br>
Settings: FTM400D/BACKUP/SETUP/SYSFTM400D.dat<br>
<br>
The size of the full memory dump minus memories and settings is 50176<br>
bytes, 0xc400, but I guess it is not all empty. I have noticed that<br>
for example incoming APRS messages are stored in memory, but I guess<br>
those would not be saved with settings or memories. Still, having<br>
separate dumps of the settings area and the channel data area should<br>
make it easier to locate those areas in the complete memory dump.<br>
<br>
I will have a look at the three files, compare them and verify the<br>
locations in the full memory dump.<br>
<br>
<br>
A closer look on the Yaesu MH-85A11U shows that it connects with a<br>
(probably modified and non standard) mini USB B only. The female<br>
connector on the radio has the usual five pins of a mini USB B, and<br>
another six pins. Since the DTMF mic that comes with the radio uses<br>
six pins I would guess that those six pins are the same as the regular<br>
mic. If I was developing hardware I would not create new stuff but<br>
rather reuse existing technology, in this case a standard USB webcam<br>
interface combined with the six pin microphone interface already in<br>
use.<br>
<br>
<br>
I opened the SCU-20 USB data cable, confirmed the presence of a<br>
PL2303. It connects using five leads both to the radio and to the USB,<br>
and I did not at this time remove the shrink tubing to check if the<br>
radio connector cable has all 10 leads or if it is a cheaper five lead<br>
cable. It would probably be quite easy to just remove the PL2303 side<br>
and make a connector for an FTDI interface instead, though. I took<br>
some photos of the inside of the interface cable before putting it<br>
back together.<br>
<div class="im HOEnZb"><br>
On Sat, Mar 8, 2014 at 4:54 PM, Johan Adler <<a href="mailto:johan.adler@gmail.com">johan.adler@gmail.com</a>> wrote:<br>
> Thank you, Tom,<br>
><br>
> In fact I just made a rough memory map earlier today, just studying the<br>
> memory dump file from the memory card with a hex editor. When comparing my<br>
> guesses with the mapping used by the FTM-350 module most major stuff seems<br>
> to be in the same places. There are new features and settings, of course,<br>
> and I will have to sort those out, but I think I can use the FTM-350 module<br>
> as a starting point.<br>
><br>
> Of course, one difference is the two different ways of accessing the memory,<br>
> cable or card.<br>
><br>
> I have not found any way of making the radio save more than one incarnation<br>
> of the memory dump, alas.<br>
><br>
> One possible interesting (non Chirp related thing) about it is the optional<br>
> camera microphone, which connects (for the camera) to what looks a lot like<br>
> a mini USB B, and where such a cable also fits. What if it would be possible<br>
> to connect some simple webcam instead of the more expensive Yaesu cam mic.<br>
> :-)<br>
><br>
><br>
><br>
><br>
><br>
</div><div class="HOEnZb"><div class="h5">> On Sat, Mar 8, 2014 at 4:41 PM, Tom Hayward <<a href="mailto:esarfl@gmail.com">esarfl@gmail.com</a>> wrote:<br>
>><br>
>> On Sat, Mar 8, 2014 at 12:54 AM, Johan Adler <<a href="mailto:johan.adler@gmail.com">johan.adler@gmail.com</a>><br>
>> wrote:<br>
>> > I have cloned the development tree and try to find how the FTM-350<br>
>> > module<br>
>> > works regarding memory download to see if can start there. I can also<br>
>> > start<br>
>> > analyzing the memory image saved to µSD, but it will be a bit tedious to<br>
>> > change one setting, turn the thing off, take the µSD card to the<br>
>> > computer,<br>
>> > copy the settings file, compare it to the previous version, put the card<br>
>> > back, turn on the radio, change another setting, and so on. :-)<br>
>><br>
>> How many memory images does it allow you to store on the µSD card? You<br>
>> make it sound like just one, unfortunately. If you can store more than<br>
>> one, you could batch a number of changes into respective files before<br>
>> copying to the computer for analysis.<br>
>><br>
>> Yaesus are pretty simple (actually, most all ham radios are). If you<br>
>> upload the memory image and include a few details like what frequency<br>
>> and PL are in the first three channels, I could probably tell you at<br>
>> least where the channel data starts and how long each record is.<br>
>><br>
>> Tom KD7LXL<br>
>> _______________________________________________<br>
>> chirp_devel mailing list<br>
>> <a href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.danplanet.com</a><br>
>> <a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_devel</a><br>
>> Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" target="_blank">http://chirp.danplanet.com/projects/chirp/wiki/Developers</a><br>
><br>
><br>
</div></div></blockquote></div><br></div>