Dear all,
I am currently working with the led_demo_qspi_alias demo project on the FRDM-K82F evaluation board to better understand how to utilize the QSPI alias region on the K82 microcontroller for debugging purposes.
I have carefully followed the steps outlined in the MBOOTQSPIUG document, but unfortunately, I have not been able to achieve the expected results. For reference, I have also described my issue in the NXP Community forum under the topic "frdmk82 troubleshooting in using led_demo_qspi_alias example project"
Now I decided to have a try by loading the project through a J-Link debugger and MCUXpresso, I observed the following behavior:
At startup, the program counter appears to be stuck in the bootloader area.
However, if I manually set the program counter to the address of main() (retrieved from the .map file), the debug session starts successfully.
Could you please clarify what might be causing this behavior? Is there a recommended way to bypass this startup issue, especially considering that the procedure in the MBOOTQSPIUG document does not seem to work in my case?
Thank you in advance for your support.
Kind regards,
Vladimir Zitoli
Hello @Vladimir_Zitoli
Thank you for contacting us.
- Have you referred to "Chapter 8 Application running on QuadSPI alias area" of MBOOTQSPIUG document ? This chapter explains how to download and run an application from the alias memory region. Please note that the steps instruction are based on the IAR IDE. If you are using MCUXpresso IDE, pay special attention when configuring the linker file.
For example:
- If your goal is simply to debug the “led_demo_qspi_alias_a000” demo on MCUXpresso IDE, please just change the Reset Handling setting to SOFT as shown below.
Change debug probe on board to CMSIS-DAP.
BR
Alice
