Hi Stuart, Re debugger suggest a $20 STM32F4 Discovery. It has a debugger uC and a STM32F4 on board. Standalone (without the SM1000) it can run STM32F4 unit tests, using stdio.h functions to/from a Host PC (semi-hosting)
You can then move a few jumpers and attach it to the SM1000 as a ST-LINK debugger/flasher, see SM1000 page "Testing and Debugging" section for links. However TBH I avoid any actual "debugging" with gdb on the STM32F4. I get the modules working on a PC first then run unit tests on the STM32F4 using semi-hosting to track down any differences. Cheers, David On 25/10/15 11:14, Stuart Longland wrote: > Hi David, > On 25/10/15 10:27, David Rowe wrote: >> 1/ Nice work on the UI improvements. I'd be happy to work with you on >> an option where we can use compressed speech prompts (my morse is rusty!). > > Yep, that would definitely be worth doing. > > Having gotten the time-out timer working, I'll probably have to put this > aside for a bit and go get some chores done for the week. > > Then I might start looking at what's needed since that would be the next > easiest option. > >> 2/ FB on taking a look at 700B mode. I described some suggested first >> steps on an email to the list on 24 Sep. Happy to work with you based >> on the results of these unit tests. I imagine I'll be up for some modem >> memory/CPU optimisation. > > Yep, I did see that. I'm looking around for a suitable debugger board, > as it's impossible to see what's going on right now. All I have is some > STM32F103 boards (Cortex M3; 64kB RAM, 512kB flash, no FPU) and the > SM1000 which has no JTAG exposed. > > The STLink/V2 programmer cables are not expensive and OpenOCD supports > them. Might be time to let some moths out of the wallet. ;-) > > Regards, > ------------------------------------------------------------------------------ _______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
