>>>> I cant upload an image into internal SRAM (AT91SAM9). >>>> it can really write only 20 bytes. >>>> load_image into internal flash area works fine.
>>> But why it doesn't fail if it writes the other regions? >>> It crashes only if it writes into internal SRAM. >> Could it be that the load_image command uses working area which overlaps > with >> the address you're trying to write, thus corrupting the algorithm? > No, I've tested writing area address:0x300000-0x300040 (SRAM start > address). > So, where is your working area? I don't know which config file you use but, > looking through some of the at91*.cfg, they generally set up working area to > 0x300000 and a few KB onwards. Have you tried moving it a bit to see if it > makes a difference. I don't see why load_image should need to use working area > so maybe it's a long shot. Worth a try anyway. :) First of all I wrote a script that can program internal flash: 1. It writes 512b into intertal flash area (load_image) 2. It touches EEFC_FCR to start writing process 3. It waites for EEFC_FSR & FRDY (finishing writing process) 4. Repeat 1 with the next 512 block until all data are written It worked pretty slowly. So then I've tested to write 32k block to SRAM (I wanted to write 1-2Kb loader). I wanted then to start the program from SRAM. But I stumbled on the load_image's trouble. Then I've returned to my old slow script. My test program countinued to grow. It ranked 2blocks, 3 blocks,... 11 blocks. Then my program began to require 14 blocks: i stubmled the problem again: If I use load_image for addresses 0x20_0000 - 0x20_1c00 - it works fine. If I use load_image for the other addresses (for example: 0x20_1c00 - 0x20_1e00 (Flash) or 0x30_0000 - 0x30_0200 (SRAM)) I have the problem. Also I've tested a few JTAGs SAM-ICE. And the problem exists for Openocd 0.4.0 and 0.5.0. -- . ''`. Dmitry E. Oboukhov : :’ : email: [email protected] jabber://[email protected] `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537
signature.asc
Description: Digital signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
