Search Results
Search results 1-4 of 4.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hello, I have been able to verify that SEGGER_OPEN_Erase is being run by j-flash now. Though as mentioned it shows success regardless if the return code is an error or ok. Thanks,
-
Hello, I'm adding support for our custom hardware using the open flashloader and using it in JFlash. (Using a J-link plus to connect if this matters) I see from here wiki.segger.com/Open_Flashloader#Init that 1 is an error code, but when I manually return an error in flash algorithm functions like SEGGER_OPEN_Read and SEGGER_OPEN_Erase, nothing happens and it shows up as successful in J-Flash. It only shows a RAMCode error with returning 1 in Uninit. (I don't know if this is a bug or what I'm as…
-
Hello, I'm creating a ramcode using the open flashloader for custom hardware using the cortex-m3 core. (ATSAM3U2C controller) We're using our own library to do operations on an external serial SPI flash, and basically just calling that library in the flashloader methods. 1. I'm wondering what can cause the following timeout error in j-link (after calling reset, then erase on j-link): Source Code (15 lines)Additional info: if I run reset then erase from the second time onwards, it only gives the …
-
Hello, I'm using the Jflash tool with a custom flashloader created using the open flash loader tool, for the Cortex-M3 r2p1. When I open JFlash I get - ERROR: Specified flashloader exceeds max. size of 64 KB. I haven't seen this in the docs so I'm asking if anyone's seen this before. I have a feeling it's because the .elf file is too large because we included our own library (this must be included). text data bss dec hex filename 13413 100 71952 85465 14dd9 open_flash_loader.elf Where does the 6…