I'm working to add in a FT-2980R subclass to the FT-2900R/1900R, and wanted to also capture the memory map images for the radio. The only way I can see to do this is by using the chirpc commands, but I can't exactly tell what is going wrong or why it's not working.

I'm not sure what you mean. The GUI downloads (and saves) whole memory images.

I am able to use the standard GUI with the modified driver file to download and upload configurations from the radio, but I can't get the command line to work.

I'm not aware of anyone that actually uses the CLI for anything, so I wouldn't say it's expected to really do much of anything. There are a few tests to make sure it's not totally broken, but certainly nothing that tests with a radio.

Why do you think you need to use the CLI? In all my development I always use the GUI because once the driver is even minimally functional the developer tools in the GUI make life much easier and faster.

chirpc -r Yaesu_FT-2980R -s COM3 --mmap 2980test.img --download-mmap The README.chirpc file suggests that it should be chirpc -r Yaesu_FT-2980R --serial=COM3 --mmap=2980test.img --download-mmap but it didn't seem to make a difference for me. I get the "Failed to read header" error from _download(radio) in ft2900.py. Again, I don't get any such errors when running the GUI application, I can download and upload modified configs perfectly.

It really should be doing the same thing as the UI and the last time I tried it (admittedly with a non-dumb radio that doesn't require the yaesu monkey dance) it worked fine. There's no other magic than what you're doing though.

--Dan