• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 585 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

MCU-PLUS-SDK-AM263X: AM2634 : Attempt To Read ROM "Version Number" Raises Data Abort Exception

MCU-PLUS-SDK-AM263X: AM263X-LP RBL log data

Jo Scho
Intellectual 300 points
Part Number: MCU-PLUS-SDK-AM263X

Hello,

I want to check the RBL log data in my SBL.
I have found the following chapter about the log data from RBL in the technical reference manual (TRM, SPRUJ17F) on page 194

I stopped the debugger in my SBL and looked into the memory browser.

Now I am a little bit confused, because I think the TRM information is not matching to the found data...

Can you give me some information about:

- log entry size , is it 8 x 32bit? with word size 32bit?
- the TRM speaks only from word 1 to word 7, what is with the 8th word?
- how many log entries can be saved from RBL, is the info 4096 bytes correct? --> that would mean 128 log entries at whole, is this correct?

thanks and best regards

Josef



  • 0
    TI__Mastermind 26145 points

    Hi ,

    This information is added with much more detail in our MCU+ Academy Training - https://dev.ti.com/tirex/explore/node?node=A__AVRt7VOfMlJSz4InbZKf4A__AM26X-ACADEMY__t0CaxbG__LATEST

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Intellectual 300 points

    Hi Aakash,

    thanks for the information.

    But I have still some questions, because the information on the academy site is in contradiction to the information of the technical reference manual and in contradiction to the memory browser view in my debug sessions.

    The first misleading information is the information about the memory location of the RBL log entries.
    The academy site says 0x80000, the TRM says 0x82800.

    What is the correct memory adress? With my AM263X-LP-board I need the address 0x82800...are there other variants/version of the RBL, which use the 0x80000?

    The second problem, I see, is the size of the "filename information". The academy says 8bit, the TRM says 32bit.
    In the memory browser of my debug session, I saw, that 8bits are not enough.

    And my third problem  is the maximum number of stored log entries? Is is 128 entries with 8 x 32bit (== 128 * 8 * 32bit = 4096bytes).

    Thanks and best regards
    Jo

  • 0 in reply to Jo Scho
    TI__Mastermind 26145 points

    Hi Jo Scho,

    #1 This is the header file from the parser -

    parse_log.h

    This parser is tested with both SR1.A and SR1.1.

    #2 The latest TRM version (SPRUJ17F – MARCH 2022 – REVISED MARCH 2024) - https://www.ti.com/lit/ug/spruj17f/spruj17f.pdf clearly covers each log data entry.

    I hope this helps.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    Intellectual 300 points

    Hi Aakash,

    thanks for the provided information and the header file, the header file helps us!

    But still one question, about the maximum number of log entries I have to expect.
    In the header file, there is a define NUM_LOG_ENTRIES, which has the value 1024.

    In our SBL we want to check, if there was an error or critical during RBL execution.
    We start parsing from the given RAM adress 0x82800 .
    Is the 1024 the used value for the maximum of possible log entries?
    We need a reliable termination criterion for ous parsing.

    The 1024 entries do not correspond with 4096 bytes, mentioned in the TRM (also in the newest version).

    Thanks and best regards

    Jo

  • 0 in reply to Jo Scho
    TI__Mastermind 26145 points

    Hi ,

    Jo Scho said:
    The 1024 entries do not correspond with 4096 bytes, mentioned in the TRM (also in the newest version).

    I will take this feedback and get this checked against the ROM code. Let me come back by tomorrow ?

    Best Regards,
    Aakash