On 14 February 2012 10:11, Spencer Oliver <[email protected]> wrote: > On 14 February 2012 01:04, Jacques Pelletier <[email protected]> wrote: >> Hi, >> >> My hardware setup is an Amontec JTAGKey tiny with openocd 0.5.0 >> I'm able to mass erase the flash and write some binaries with size < 1024 >> bytes. >> >> Any binaries with size greater than 1024 fail to program and openocd gives >> sticky errors. If I split the binary into 1024 chunks and write them in >> successive location, the write operations succeed and the program runs fine. >> >> The LM3S101 has 8k flash in 8 1k blocks, and 2k of SRAM. Can the small size >> of >> the RAM be a problem for programming the flash? >> >> It seems to me that this is a software problem and I could use some time to >> try to fix this. I looked a bit in src/flash/nor/stellaris.c. >> > > I am guessing that the working area is incorrect. > The default WORKAREASIZE is 8k unless changed by your config - perhaps > this needs changing to a safer smaller value. > > For testing try adding this to your config: > set WORKAREASIZE 0x800 >
I have uploaded a patch that changes the default working area: http://openocd.zylin.com/458 If you are able to test that would be great. Cheers Spen ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
