• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1530 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:

AWR1642: RPRC Image format

AWR1642: RPRC Image format

Kevin.Y
Intellectual 455 points
Part Number: AWR1642

Hi,

I'm reading Image Creator User Guide and need to clarify the header length and the word "size".
RPRC format has RPRC header and Section Headers.

Q1: Are those headers always 24 bytes long?

Q2: In the section header, there is "Section size". Does this value indicate the exact data length?
For instance, if the value of section size is 0x3C (60), then is the length of the section data after the section header 60 bytes?

Best Regards,
-Kevin

  • 0
    TI__Mastermind 21025 points
    Hi Kevin,

    Q1: Yes, the RPRC header is fixed at 24 bytes.

    Q2: Yes, the section size is the number of bytes in the section, as you describe. It does not include any section header bytes.

    -dave
  • 0 in reply to db_woodall
    Intellectual 455 points

    Hi Dave,

    Then I'm getting confusing.....

    The follwing is the first some words data from srrdemo_16xx_mss.bin.

    0000: 52 50 52 43 70 E5 00 00 00 00 00 00 04 00 00 00
    0010: 01 00 00 00 00 00 00 00

    0018: 00 00 00 00 00 00 00 00 3C 00 00 00 00 00 00 00
    0028: 00 00 00 00 00 00 00 00

    0030: 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5
    0040: 18 F0 9F E5 18 F0 9F E5 18 F0 9F E5 B0 F1 1F E5
    0050: 70 E5 00 00 50 B0 00 00 50 B0 00 00 50 B0 00 00
    0060: B8 B0 00 00 50 B0 00 00 A8 D1 00 00

    006C: 00 00 00 00 00 01 00 00 00 00 00 00 E4 21 01 00
    007C: 00 00 00 00 00 00 00 00 00 00 00 00 2D E9 F8 43
    ........

    RPRC header is from 0x0000 to 0x0017 and Seciton header is from 0x0018 to 0x002F.
    Section length should be 0x0000003C (60) so the section data will start at 0x0030 to 0x006B.

    Then the next section start but the section length is 0x00000000 and some values 0x000121E4 in Reserved.

    So I'm confusing now.....

    Is my analysis correct?

    Best Regards,
    -Kevin

  • 0 in reply to Kevin.Y
    TI__Mastermind 21025 points
    Looks right to me. What version SDK are you using? I've answered based on examining the source code for the tool; I'm checking to see if perhaps it has changed from one version of the SDK to the next. If I look at a .bin file produced with SDK 2.0 I see the same thing.

    -dave
  • 0 in reply to db_woodall
    Intellectual 455 points
    Hi dave,

    As we can see, there is a new section so the length should not be ZERO but actually it is ZERO and some values are in the reserved area.
    So I think I did analyze in wrong way.
    I"m using the latest SDK ver 2.0.
    Can you give me any clue on this?

    -Kevin
  • 0 in reply to Kevin.Y
    TI__Mastermind 21025 points
    Sorry for the delay, I'm checking on this with the team that created and owns the tools.
  • 0 in reply to Kevin.Y
    TI__Mastermind 21025 points

    Hi Kevin,

    The answer is that the actual section length is always padded to a multiple of 8 bytes, even though the section_length field does not reflect the padding.  This forces each section start to begin on an 8 byte aligned position in the bin file.

      -dave

  • 0 in reply to db_woodall
    Intellectual 455 points
    Hi dave,

    Thank you for the information.
    I will check my analysis.

    -Kevin