On Sunday 10 January 2010, Freddie Chopin wrote: > The short version is like this - after power-up of JTAG and STM32 board, > the first "load" from gdb just fails with "cannot write <first address> > ..." error. At this moment I'm not sure whether it's a reset of JTAG > "after power-up" issue (the problem which I described some months ago, > which seems fixed) or a STM32 "after power-up" issue.
Hmm ... one place to start would be turning on debug level 3, and maybe eventually JTAG I/O tracing, and posting the log showing the activity involved in that "cannot write" error. There's surely more information available inside the OpenOCD daemon! Like, in particular, what makes it believe that it can't write. When, as you imply, it works just fine later on ...:) Does it matter whether you're loading code to SRAM or to flash? FWIW my rather limited set of Cortex-M3 devices here suggests this is not a general issue; I've never seen this. - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
