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.
-
Yes, the pre-compiled loader works perfectly! And when I erase the chip in Commander, it recognizes the Dual Bank sectors correctly this time. Thanks. Please mark this as solved
-
To reproduce the issue, switch your Eval Board to Dual Bank configuration and try debugging with Jlink
-
After a few more tests. I believe I've isolated the issue. I'm required to run the program in the DUAL Bank configuration and I think JLINK does not not that. If I configure it to 256-bit Single Bank mode, jumping to main app is no problem. So it has to be related to the Dual Bank configuration done though the option bytes. How do make the JLINK aware of this configuration? I also observed that when I erased the controller through Jlink Commander, it would erase it according to the Single Bank s…
-
Hi, I'm using the J-Link EDU and STLink debugger present on the Nucleo boards from ST. For testing, the bootloader code is present at 0x8000000 and just jumps to 0x8020000 where the main app code is present. When I use the Jlink EDU, it can't program the flash at 0x8020000 every time successfully and if i modify the program and start debugging, the Jlink erases the flash but does not program it successfully and after the bootloader makes the jump, the MCU gets HardFault. Now this happens whether…