• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 84 subscribers
  • Views 265 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.

TMS320F28P650DK: DCAN Flash Kenel + ROM Bootloader Issues

Ayden Bourdeau
Prodigy 110 points

Part Number: TMS320F28P650DK

Hi TI E2E support,

Over the last few weeks, I have been working trying to DFU working using the DCAN kernel on my P65x. I have successfully flashed both the kernel and my custom application over CAN using PCAN and the following documents.

  1. Application Note CAN Flash Programming of C2000 Microcontrollers 
  2. C2000™ Software Controlled Firmware Update Process

I built and tested the example flash kernel dcan_flash_kernel_c28x_dual_ex5 and have modified my application to output the specific sci-8 format .txt file in the post-process build steps. Whilst running the flash kernel example project, I am able to update to my application using a BTR of 0x7FC0. No issues while running the example program in debug mode.

At this point, I am confident that my kernel and application are built successfully. I am now trying to move over to remote firmware updating using a process similar to (2) where in my application i toggle the GPIO to charge the caps on the bootpins and trigger a reset to bring the device into the CAN bootloader for an update. Unfortunately, at this point even when I sent the kernel / application nothing happens. I have validated each of the following

  • BMSP OTP Programmed to -> 0x5AFF4854 (GPIO 84 index 0 GPIO72 index 1) for the boot table
  • BOOTDEF OTP Programmed to -> 0x00066203 (Boot order is Flash ALT 0, CAN ALT 3 (matches my CAN pins), SPIA ALT 0 (future development)
  • My application does trigger the appropriate pins, reset and bring the device into my bootloader based on an incoming message

I am convinced this is a mistiming issue. I have a few follow-up questions before proceeding with debugging that I was not able to find answers for.

  1. Does the ROM bootloader require any specific timing requirements? I see on page 1074 of the P65 TRM, the ROM bootloader loads the kernel in at 100kbps, but correct me if I am wrong, the kernel will load into RAM at the hardcoded rate regardless of what I change my bitTimingReg value in (see below), then once the kernel is loaded it will resync to the bit timing for my application loading process to the value of this BTR specified in my kernel build. Please see the picture below.
  2. I have attached the first few bytes of my build flash kernel. The BTR has been modified to match what I put in DCAN BOOT in the first picture for the dcan example project. If the ROM bootloader requires the timing to match (page 1074 of the TRM) does the first bytes in my DCAN kernel need to match this BTR of the ROM?

image.png

image.png

Thanks for you help. Let me know if you need any more information.

  • 0
    TI__Mastermind 40103 points

    Hello Ayden,

    This thread has been assigned to the expert for further review and action. Please note that our team's response times may be slower than usual due to the holiday season. We will get back to you as soon as possible and appreciate your understanding in this matter.
    Thank you for your inquiry and we look forward to assisting you soon.

    Best Regards,
    Zackary Fleenor

  • 0 in reply to Fleenor
    TI__Expert 4530 points

    Hi Ayden,

    Ayden Bourdeau said:
    Does the ROM bootloader require any specific timing requirements? I see on page 1074 of the P65 TRM, the ROM bootloader loads the kernel in at 100kbps, but correct me if I am wrong, the kernel will load into RAM at the hardcoded rate regardless of what I change my bitTimingReg value in (see below), then once the kernel is loaded it will resync to the bit timing for my application loading process to the value of this BTR specified in my kernel build. Please see the picture below.

    The ROM bootloader operates at 100kbps by default. Your host programmer should send the application at this rate up until the bit timing value is sent, then it should reinitialize itself at the higher bitrate and continue sending the kernel image.

    Ayden Bourdeau said:
    I have attached the first few bytes of my build flash kernel. The BTR has been modified to match what I put in DCAN BOOT in the first picture for the dcan example project. If the ROM bootloader requires the timing to match (page 1074 of the TRM) does the first bytes in my DCAN kernel need to match this BTR of the ROM?

    Instead of passing your bitrate into the DCAN_Boot function directly, adjust the CAN_CALC_BITRATE, CAN_CALC_CANCLK, and CAN_CALC_BITTIME parameters in ex_5_bootloader_can_timing.h and pass 0 to the function. This will automatically compute the correct timing value and assign it to the register.

    Best,

    Alex