[Lucas Rolfes]

Interesting bit of follow up – it appears as though this process will not work with Jlinks as it exists today.

I moved over to an STLINK, and kept nearly identical code on both sides, and nearly identical configurations beyond the necessary means to use the JLINK, and the tools no longer error out in the manner that I was seeing before.

Also from the debug logs, I am seeing notes programming flash sections of 20 bytes (which is my test usage size), so far that I can tell things should be working correctly now.

Now my sample implementation appears to not be either memory mapping correctly or the .elf is not properly loading, data into the QSPI, but that is my problem to solve.

 

Thanks for the support!

[Lucas Rolfes]

Hello again.

 

Thank you for the suggestion of checking the telnet connection. I was able to probe the address that was claiming the device was failing to write to – 0x2001fffc , and it did return *a* value indicating that there was not an error.

GDB also did not have issues probing that address nor nearby addresses.

I ran this test via the primary application, with the flash plugin command removed to simplify things.

Whats interesting is 0x2001fffc is the end of the DTCRAM, and it appears to occur even if I remove the that reference in both linker files.

This issue only occurs when including the command -c “flash bank qspi plugin 0x90000000 0 0 0 0 C:/Users/Public/FlashLoader.elf”

It appears as though the flash loader plugin is communicating and working mostly as I would expect, as if I remove the call to FLASHPlugin_InitDone() from main.cpp’s main() function, the tool does claim it is missing.

I can’t say I know well enough how the flash plugin operates, but I did add a LED toggle for a few seconds inside of the main loop of the flash loader .elf output, and I did not see the LED toggle at least indicating to me the file was not loaded into memory prior to the main app.

Is there maybe a command I can issue inside of the FlashLoader.elf to confirm that it is being executed / entered correctly?

 

[Lucas Rolfes]

Hello,

 

Thanks for getting back to me!  I’ve attempted to run the following:

openocd.exe -c “gdb_port 64986” -c “telnet_port 64984” -c “debug_level 3” -f interface/jlink.cfg -c “transport select swd” -c “adapter speed 3000” -c “mdw 0x2001ffc” -c “exit”

and I get the error message that it does not understand the command mdw. Is this an inappropriate usage of mdw? If so, how would I get it to execute properly?

I am not explicitly setting the SWD pins, so they are not being configured via either the flash loader application nor the main application. I will explicitly set those and let you know if that changes anything.

Thanks,
Lucas

 

[Author]

Posts