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.

CAN boot loader questions

Hi everyone,

My custoer does not want to implement the JTAG circuit on production board and he want to update only CAN port.

So I suggested to him to write CAN boot loader before board mounting of the device(TMS570LS313).

Then please let me following questions.

Q1.

Are there any application note for writing two project(boot & app) in a single device?

My custoer don't want to erase the CAN boot code but Example project of the following link may erase the CAN boot code.

processors.wiki.ti.com/.../TMS570_Hercules_MCU_Bootloader

Q2.

If he remove JTAG circuit and write programs with CAN port,

Which do you recommend (A) and (B).

(A) every time load the boot code

(B) protect the boot code (using Flash Bank Sector Enable Register) and to only load the application code.

I want to suggest an easy way to my customer.

Best regards,
Sasaki

  • Hi Sasaki,

      Here is the link to the app note. 

    Normally the bootloader is stored in the first few sectors of the flash bank. They are loaded to the flash via the JTAG interface. The bootloader setups the CAN bus to download the application code. There is no need to erase the bootloader. Perhaps I'm not understanding what you meant by erasing the CAN boot code. I also don't understand what you meant by (A) every time load the boot code.  Can you elaborate a bit? Hopefully if you follow the example in the app note it becomes clear what to do.

  • Hi Charles,

    Thank you for your information.

    I'll try to read this app note.

    Charles Tsai said:
    Perhaps I'm not understanding what you meant by erasing the CAN boot code. I also don't understand what you meant by (A) every time load the boot code.

     I wanted to prevent the that my customer accidentally erase the CAN boot code.

    For that reason, I gather information about  it.

    Thanks & regards,

    Sasaki