SPRAD51A December   2023  – April 2024 F29H850TU , F29H859TU-Q1 , TMS320F2800157 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F28P659DK-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Programming Fundamentals
  6. 3ROM Bootloader and Hex Utility Usage
  7. 4DCAN Flash Kernel
    1. 4.1 Implementation
      1. 4.1.1 Custom Flash Bank and Sector Erase
      2. 4.1.2 Application Load
  8. 5MCAN Flash Kernel
    1. 5.1 Implementation
      1. 5.1.1 Custom Flash Bank and Sector Erase
      2. 5.1.2 Application Load
  9. 6Example Implementation
    1. 6.1 Device Setup
      1. 6.1.1 Flash Kernels
      2. 6.1.2 Hardware
    2. 6.2 Host Application: dcan_flash_programmer
      1. 6.2.1 Overview
      2. 6.2.2 Building and Running dcan_flash_programmer Using Visual Studio
      3. 6.2.3 Running dcan_flash_programmer for F28003x
      4. 6.2.4 Using the Project With DCAN Bootloader
      5. 6.2.5 Using the Project With CCS
    3. 6.3 Host Application: can_flash_programmer [MCAN]
      1. 6.3.1 Overview
      2. 6.3.2 Building and Running can_flash_programmer Using Visual Studio
      3. 6.3.3 Running can_flash_programmer for F28003x
      4. 6.3.4 Using the Project With MCAN Bootloader
      5. 6.3.5 Using the Project With CCS
    4. 6.4 Application Load: CPU2 Image
      1. 6.4.1 Combining Two Images (.txt)
  10. 7Troubleshooting
    1. 7.1 General
    2. 7.2 DCAN Boot
    3. 7.3 MCAN Boot
  11. 8References
  12. 9Revision History

7.1 General

Question: I cannot find the kernel projects, where are they?

Answer:

Device Build Configuration Location
F28003x RAM C2000Ware_x_xx_xx_xx > driverlib > f28003x > examples > flash
F28P65x RAM C2000Ware_x_xx_xx_xx > driverlib > f28p65x > examples > c28x_dual > flash_kernel

F280015x

RAM

C2000Ware_x_xx_xx_xx > driverlib > f280015x > examples > flash

Question: What are the first things I should check if the flash kernel does not download?

Answer:

  • One area of the program to check would be the linker command file - make sure that all flash sections are aligned to proper boundaries. The F28P65x and F280015x DCAN Flash Kernels display the 512-bit programming capability of their respective Flash API. Thus, applications loaded with these two kernels should be 512-bit aligned. Similarly, applications loaded with the F28P55x MCAN flash kernel should be 512-bit aligned. In SECTIONS, add a comma and "ALIGN(32)" after each line where a section is allocated to flash.

    For all other flash kernels mentioned in this document, the 128-bit programming function of the Flash API is used. Thus, applications loaded with these kernels should be 128-bit aligned. In SECTIONS, add a comma and "ALIGN(8)" after each line where a section is allocated to flash.

  • One other common issue users encounter is that they are not using the correct boot pins for the CAN/MCAN boot mode. For example, on the F28003x devices, MCAN boot has three options for GPIO pins to use. Make sure that the pins for the default option are not being used for something else.
  • When using long cables, use a lower baud rate to get rid of noise.
  • For baud rate and connection issues, try running the CAN/MCAN loopback and transmit examples for the device (you should be able to find these in C2000Ware in the driverlib/examples folder for your device).
  • The operational CAN-FD clock range of the PEAK PCAN USB-PRO FD Analyzer is 20MHz to 80MHz. The MCANxBIT Clock of the device must match the CAN-FD clock frequency of the PEAK tool in order for frames to transmit.
  • Both the dcan_flash_programmer and the can_flash_programmer require use of the PEAK PCAN USB-Pro FD Analyzer, as the tool is capable of transmitting standard CAN frames and CAN-FD frames. The PEAK PCAN USB FD device is also compatible.

Question: I have combined the application images yet still cannot program, how can this be resolved?

Answer: Be sure that the first image in combined .txt file contains CPU1's image, followed by CPU2's image.