This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2634: UNIFLASH Memory Read Is All Zeros

Part Number: AM2634
Other Parts Discussed in Thread: UNIFLASH

Hello,

I made a multi-core appimage file.

Flashing the appimage with SBL to external flash reports success:

Indeed Core 0 appears to run (flashing LED) after power on reset in QSPI boot mode. However the other cores do not run so the first thing to check is the contents of the RAM where the program code is loaded.

Since I know Core 0 runs, I wanted to verify that UniFlash reads plausible contents from memory. Much of Core 0 code is loaded from 0x7010 0000 as you can see from the map file:

So I clicked the Memory in UniFlash then requested memory read from 0x7010 0000. However, all memory is just 0x0.

Since Core 0 is running, then this memory cannot be zero after the SBL runs and loads the program from external flash.

Note that UniFlash does read correct vector tables from 0x0 so in principle UniFlash is able to read the memory.

<Question>

Why does UniFlash read all zeros from the Core 0 program .text RUN address?

Thank you.

  • I just discovered the reason. When I click 'Read Target Device', I notice that there is a bunch of GEL file execution which takes place. This basically resets the processor and wipes the program from RAM:

    If I edit C:\ti\uniflash_8.5.0\deskdb\content\TICloudAgent\win\ccs_base\emulation\gel\AM263x\AM263x.gel such that:

    #define Enable_OnTarget_Connect 0

    Executing the same 'Read Target Device' gives me the expected results:

    <Feature Request>

    The Memory feature should be non-intrusive in my opinion. Please prevent any reset action (or offer the option to prevent) when using the Memory feature. It just needs to connect and read memory. In other words the equivalent of editing the GEL file as above.

  • Hi Kier,

    We will take notice of the same and thanks for sharing the same with me.

    Best Regards,
    Aakash