• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 358 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.

AWRL1432: Uniflash

Shawn Li(Radar)
Intellectual 865 points
Part Number: AWRL1432
Other Parts Discussed in Thread: UNIFLASH

Hi team,

Customer is using Uniflash 8.4.0 to download the bin file. Their process is failed, and the console outputs are as picture shows. But I tested Uniflash 8.4.0 by flashing KTO appimag, it works well. Customer's environment is Windows10, no device using serial port except 1432 evm. Please help to find a solution.

Regards.

Shawn

  • 0
    TI__Genius 12986 points

    Hey Shawn,

    Thanks for reaching out to us! This appears to be caused by an issue due to the meta header generated when calling the image creator tools. Additionally, the image creator should generate a .appimage for SDK 5 devices, so this file being a .bin seems to imply this may have been generated with the SDK 3 image creator somehow. Note that you can use .bin files with an SDK 5 device as long as it was built using the SDK 5 image creator tools. This leads me to a few questions:

    • How was this binary created?
      • Did the customer import the MCAN external read and write driver example and rebuild it?
      • Are they calling the image creator tools with their own custom file?
    • If this is from the driver example:
      • Did they modify the makefile_ccs_bootimage_gen file?
      • What version of the SDK is being called when building the project?
        • You can check the compiler by right clicking on the project -> Properties -> Build -> Arm Compiler and look at the flags to see what SDK version is being used
    • If this a custom build:
      • What is their build file for generating the final binary?

    I hope to hear from you soon!

    Regards,

    Kristien