• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 29 subscribers
  • Views 103 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS570LS1227: Code Output Text Generation Differences

Onur Duran
Prodigy 20 points
Part Number: TMS570LS1227

Hi All,

I try to  do CAN bootloader for TMS570ls1227. Firstly I am writing bootloader code at memory map of microcontroller, then I am writing app code wit debugger where to selected address(0x10000). You can see memory status at different style at IMG_1, IMG_2, IMG_3 . Then I am generating code output as a text. After generating I wrote whole text to flash of microprocessor and code didn't work. Because of this, I found difference of text code  and debug memory placement. For example  0x10000 address's data writes at end of line 2 (you can check it on IMG_5) 0x10020 address's data have written at line 327  (you can check it on IMG_4).I think code generation tool produce the code different style from the memory map order. 

Can you offer anything about this? I hope, I can explained the situation as truly.

  • 0
    TI__Guru**** 186196 points

    Hi,

    The main flash instruction memory is addressed starting at 0x00000000 by default. This is also the reset vector location – the ARM Cortex-R4F processor core starts execution from the reset vector address of 0x00000000 whenever the core gets reset. You need to program a interrupt vector table to 0x00000000~0x00000020.

    How did you generate text file for your code? Why do you need a text format?

  • 0 in reply to QJ Wang
    Prodigy 20 points

    Hi,

    My GUI read the text and sends to datas from CAN BUS to microcontroller for bootloading process. I know, normally code start from 0x00000000. TMS570ls1227 has one bank to write the code, so I am using different address of memory both application code and bootloader code. I added my cmd file  foto to here. 

    I am trying to write my application since the 0x10000 address.You can see my application code's memory settling at previous post.

    My question is why memory settling of code at debugger  is  different from text output of compiler? (IMG_4 and IMG_5 text out of same code, IMG1-2-3 memry seetling at debug mode of same code.) By the way can you read the photos at first post, is it clear?

    I added my text generating settings at below as second photo.

         

  • 0 in reply to Onur Duran
    TI__Guru**** 186196 points

    II don't know the format of the text file exported from post-built. The text file includes the addresses and header. Does your bootloader program the header to flash too? Can you show text file content in 32-bit mode?

    I read the photo in your prior post. I don't see difference between the contents at 0x10000 and 0x10020:

    In your memory browser window:

    In your text file:

    The first 4 bytes are the address 0x10000, and following is the data: 0xEA0056A5

    The first 4 bytes are the address 0x00010020, and following are the data: 0x00000000 and 0x08001500

    I don't know why the address 0x10000 is at line #2, but the address 0x10020 is at line #327. What are between?

    Why don't use the binary file as used in bootloader example?

  • +1 in reply to QJ Wang
    Prodigy 20 points

    Hi, 

    I solved my problem. I changed to text generation settings at  previous pic to new settings. You can see my new code generation settings at below picture.

    I told you, our bootloader GUI can send the code output as a text, so I am using text output style for bootloader process. On the other hand after I changed code output settings like below, my memory code sequence and my text output have were same.