MCU-PLUS-SDK-AM263X: How to debug a Flash region?

Sharmili Narayanamurthy

Part Number: MCU-PLUS-SDK-AM263X
Other Parts Discussed in Thread: UNIFLASH

Hi expert,

As per the previous post - by changing the GEL file mode bug, I am able to debug a multi-core project using CCS by flashing the SW to the L2OCRAM of size 2MB (0x70000000 to 0x701FFFFF).
But is there any possibility to flash a SW to the External Flash region & to stay in debug mode in the CCS.

The purpose of this question is to know whether SWs with size more than 2MB can be in debugging mode & to have a clear understanding of how the memory in the flash region is utilized.
PS. I am able to flash the SW to external flash region in QSPI mode via UART terminal & via JTAG as well. I am looking for debugging options with SW getting executed from External flash.

Could anyone let me know any leads on this? TIA.

Regards,
SN

over 3 years ago

0 Daniel Bermudez over 3 years ago

TI__Expert 8090 points

Hi SN,

The debug view/context cannot exist from external flash itself.

However, we have an FAQ that provides instructions on entering a debug state upon execution of the sbl while there is an image present in the external flash, please refer to:

(+) [FAQ] MCU-PLUS-SDK-AM243X: How to debug sbl_qspi (for am263 and am273) or sbl_ospi (for am243) or an application which is booted via OSPI/QSPI boot ? - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

Best,

Daniel

0 Sharmili Narayanamurthy over 3 years ago in reply to Daniel Bermudez

Prodigy 110 points

Hi Daniel, I had referred to the link FAQ & tried following the steps mentioned. Thanks for that - I have tried them already.

The PC was always pointed towards "Bootloader_socSecHandover" API instead of Loop_forever() as mentioned in that FAQ..
And went outside the visibility when executed.

I wanted to confirm with the steps to be followed.
1. I was able to see that it is the same way for SBL example or any application that is booted via QSPI.
Which means if the application has to be debugged - the loop_forever() has to be added in the Application's main(). Is my understanding correct?

2. If application is added with loop forever, after flashing the SW through SBL prebuilt configuration - while loading the symbol of the application, the boot mode to be in 1101. Is that correct?

Snippet below for your reference:

Please let me know if there is anything else that I am missing.

Thanks in advance.

Regards,
SN

0 Daniel Bermudez over 3 years ago in reply to Sharmili Narayanamurthy

TI__Expert 8090 points

Hi SN,

Just followed the steps on the FAQ on my side using a hello_world example to be able to help you:

Sharmili Narayanamurthy said:
1. I was able to see that it is the same way for SBL example or any application that is booted via QSPI.
Which means if the application has to be debugged - the loop_forever() has to be added in the Application's main(). Is my understanding correct?

That is correct, just call it as the first function in you main() file

Sharmili Narayanamurthy said:
2. If application is added with loop forever, after flashing the SW through SBL prebuilt configuration - while loading the symbol of the application, the boot mode to be in 1101. Is that correct?

Yes, the boot mode should be QSPI boot mode (1101).

After you load the symbols, follow these instructions:

Pause the application, you should see that you are stuck in the loop_forever() function
open the Varibales tab in CCS
change the value of "loop" to "0" and press enter
Press the "Step Return" (F7) button to exit the loop fucntion
At this point you should be back in main and able to step through your application

Please try the above extra steps and let me know if you still experience the same issue.

Best,

Daniel

0 Sharmili Narayanamurthy over 3 years ago in reply to Daniel Bermudez

Prodigy 110 points

Hi Daniel, thanks for the response.

I have re-tried the steps & hopefully I have executed each step appropriately.

But then - the behaviour is same. It doesn't work as per the expectation.
For a SBL build, it is the API that I have quoted in my previous reply that is hit all the time.
For an application build, it is always inside this function below:

Regards,

0 Daniel Bermudez over 3 years ago in reply to Sharmili Narayanamurthy

TI__Expert 8090 points

SN,

I will reach out for help on this. Please allow until Tuesday to come with a resolution

Thanks,

Daniel

0 Aakash Kedia over 3 years ago in reply to Daniel Bermudez

TI__Mastermind 26145 points

Hi Sharmili Narayanamurthy,

Did you rebuilt your SBL and checked if the symbols are matching correctly with your program ?

Best Regards,
Aakash

0 Sharmili Narayanamurthy over 3 years ago in reply to Aakash Kedia

Prodigy 110 points

Hi Aakash,

I am not sure on how to confirm whether the loaded symbol (.out file) matches correctly to the program.
Could you please let me know how to get this point ensured.

Thanks & Regards,
Sharmili Narayanamurthy

0 Aakash Kedia over 3 years ago in reply to Sharmili Narayanamurthy

TI__Mastermind 26145 points

Hi Sharmili Narayanamurthy,

If you have loaded a function with loop_forever at the very start of your code, the code is expected to be in a while loop. The disassembly will show you the same software being executed in a loop. Do you see that ?

Best Regards,
Aakash

0 Sharmili Narayanamurthy over 3 years ago in reply to Aakash Kedia

Prodigy 110 points

Hi Aakash,

As you could see the snippets from my previous replies - the SW doesn't get into the loop at first place. And the disassembly doesn't show that as well.
The images from my previous replies have the Disassembly captured.

Thanks & Regards,
Sharmili Narayanamurthy

0 Aakash Kedia over 3 years ago in reply to Sharmili Narayanamurthy

TI__Mastermind 26145 points

Hi Sharmili,

Is this the TI-SBL that you intend to debug ? or is this the Application that you intend to debug ?

Best Regards,
Aakash

0 Sharmili Narayanamurthy over 3 years ago in reply to Aakash Kedia

Prodigy 110 points

Hi Aakash,

It is the TI SBL QSPI that I am trying currently to begin with.

Thanks & Regards,
Sharmili Narayanamurthy

0 Aakash Kedia over 3 years ago in reply to Sharmili Narayanamurthy

TI__Mastermind 26145 points

Hi Sharmili,

Can you please answer the following questions ?

1. Can you point out if you are using TI-EVM ? If yes, which one ?
2. Which example are you flashing ? Can you share the path of the example ?
3. Can you also share which method are you using to flash the image ? Is it UART-UNIFLASH or JTAG-UNIFLASH ?

Best Regards,
Aakash

0 Sharmili Narayanamurthy over 3 years ago in reply to Aakash Kedia

Prodigy 110 points

Hi Aakash,

1. Yes, it is AM263x - Control Card.
2. SBL QSPI from the SDK - C:\ti\mcu_plus_sdk_am263x_08_03_01_05\examples\drivers\boot\sbl_qspi\am263x-cc\r5fss0-0_nortos
3. I am using the UART UNIFLASH method.

Thanks & Regards,

Sharmili Narayanamurthy

+1 Aakash Kedia over 3 years ago in reply to Sharmili Narayanamurthy

TI__Mastermind 26145 points

Hi Sharmil,

Is the boot mode correctly set to QSPI ?

Ref - https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/08_04_00_17/exports/docs/api_guide_am263x/EVM_SETUP_PAGE.html#autotoc_md30

I saw the message that it is set to 1101 which is not the right. Can you recheck that ?

Best Regards,
Aakash

0 Sharmili Narayanamurthy over 3 years ago in reply to Aakash Kedia

Prodigy 110 points

Hi Aakash,

That's a good catch. The boot mode has been an issue.
By changing the boot mode to 0010, it works as per expectation and enters into loop_forever().

Thanks for your time and effort. This resolved my problem.

Regards,
Sharmili Narayanamurhty