On Mon, Oct 7, 2013 at 5:50 AM, Nader <[email protected]> wrote:
> Hi Guys,
>
> I was able to compile the latest dirty version, and just a feedback,
> the errors still there for my case .
>
> I am willing to try anything you throw on me ... :)
>
Ok, lets try the following steps, <file.elf> is the >1MB file you're having
problems with.
Have you tried erasing/programming from the OpenOCD telnet prompt to rule
out GDB related problems? You can then try to do a mass erase instead of a
sector-by-sector erase (I think the stm32f2x driver has that feature,
should be smth like 'stm32f2x mass_erase 0'). Any errors?
Then check if it was erased ok with 'flash erase_check 0'. Was it?
Next step, program the image using 'flash write_image <file.elf>'. Key
point here, don't specify 'erase' as an option, we've already done that
step. Any errors?
Finish off with 'verify_image <file.elf>'. Success?
If this works it might be a problem with the sector erase function. Check
that with 'flash write_image erase <file.elf>' which should be similar to
what happens during GDB load.
Another observation about the xPSR info:
> xPSR: 0x01000000 pc: 0x08001b10 msp: 0x20030000 (when it is working ok)
> xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc (when it is NOT)
>
> Both PC and SP are bogus.
>
Because at least the first sector was erased successfully and the erase
probably failed when crossing the bank boundary.
/Andreas
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
