• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 375 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.

hexAIS hex6x questions

Eric Bryan
Expert 1045 points

1)  When using hex6x, will the records created always start on a 32bit address boundary.  This seems to be the case and we are using this as a rule in the our bootloader that loads the code.  I just wanted confirmation that this is the case.

2)  I have see reference in some of the TI docs that there is another tool for creating AIS boot files called AISGEN.  I would like more control over the AIS boot code that is generated when I converter my bootloader code than I get from the hexAIS.exe.  I would like compile in a version# at a know location in the Flash Memory the DSP boots from.  Is this the right application to use or is there another I should try?  Is there a specific version of this app for the DM6435/DM6437?

3) Is there a single concise reference for the AIS format?  I have been unable to find complete documentation on the AIS format that lists all the opcodes.  I am using the DM6435/DM6437 if that matters.  I've tried manually disassembling the AIS code generated for our project and it has some calls that I could not find documented.

Eric Bryan

 

 

  • 0
    TI__Guru**** 249680 points

    Eric Bryan said:
    1)  When using hex6x, will the records created always start on a 32bit address boundary.  This seems to be the case and we are using this as a rule in the our bootloader that loads the code.  I just wanted confirmation that this is the case.

    It is not guaranteed.  If a section comes through that does not start on a 32-bit boundary, then the corresponding hex6x output will not start on a 32-bit boundary either.  However, most sections created for execution on C6000 devices  tend to start on 32-bit boundaries.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1045 points

    Want to be clear here.  I am asking about the record produced by hex6x with default settings.  Is the record stored in the rom (as opposed the the location specified by the record) always on a 32 bit boundary.

     

  • 0 in reply to Eric Bryan
    TI__Guru**** 249680 points

    The record produced by hex6x directly uses the address of the code or data from the linked executable (usually a ".out" file).  Such addresses are not guaranteed to be on 32-bit boundaries.  Thus the address of the records produced by hex6x are not guaranteed to start on a 32-bit boundary.  

    Sorry for the delayed response ...

    -George