• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 30 subscribers
  • Views 370 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.

AWR2944: FLASHWRITER

Mike Unger
Prodigy 75 points
Part Number: AWR2944
Other Parts Discussed in Thread: UNIFLASH

Hi,

I am trying to use the FLASHWRITER to program a binary file and am having trouble.

When I use it to program a .tiimage file the syntax in the .cfg file is like this ...

--file=../../../../release/SBL_QSPI.tiimage --operation=flash --flash-offset=0x0

But, think I need something different for a straight binary file. I've been searching for the correct syntax but w/o success.

Please advise.

Thanks.

Mike

  • 0
    TI__Guru* 91206 points

    Dear Mike - 

    Thanks for the post and welcome to E2E! 

    Please check and see if this assists you: 

    C:/ti/mmwave_mcuplus_sdk_04_04_01_02/mcu_plus_sdk_awr294x_09_00_00_15/docs/api_guide_awr294x/TOOLS_FLASH.html#BASIC_STEPS_TO_FLASH_FILES 

  • 0
    Prodigy 75 points

    Hi John,

    Thanks for your response. Yeah, I always have the hardest time finding those guides. Anyway, at first look I'm not seeing anything in there about binary files. My config file is like this:

    --flash-writer=../../../../release/SBL_UART_UNIFLASH.tiimage

    # Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

    # send the application image to flash. Flash it at 0xA0000 as the SBL expects it at this location
    --file=../../../../release/ppar_v6_default.bin --operation=flash --flash-offset=0x1F0000
    #--file=../../../../release/MCENT.appimage --operation=flash --flash-offset=0xA0000

    I have the one line flashing MCENT.apimage commented out, used it as a test to make sure I have the path correct.

    The error I get is:

    PS C:\Gen40_TI\gen40_dev\sw>
    PS C:\Gen40_TI\gen40_dev\sw> cmake --build --preset deploy-awr-ppar
    [0/1] cmd.exe /C "cd /D C:\Gen40_TI\gen40_dev\sw\boot\scri...t/scripts/uart_uniflash.py -p COM6 --cfg=uni_ppar_awr.cfg"
    Parsing config file ...
    Parsing config file ... ERROR. 1 error(s).

    [ERROR] Parsing error found on line 21 of uni_ppar_awr.cfg
    [ERROR] File not found !!!

    line 21 is the one that calls out the .bin file, I have, of course, checked the name a million times. Slight smile

    Again, is there some kind of directive I need on the --file line to indicate that I am referring to a binary file?

    Thanks.

    Mike

  • 0 in reply to Mike Unger
    TI__Guru* 91206 points

    Mike - 

    From flash tool error messages and solutions:

    Check the message that is printed, and edit the config file to fix the parsing errors. Make sure to specify file paths with forward slash /, including in Windows. The default config file should not have any errors though.

    I see this line in your post: cmd.exe /C "cd /D C:\Gen40_TI\gen40_dev\sw\boot\scri...t/scripts/uart_uniflash.py -p COM6 --cfg=uni_ppar_awr.cfg" 

  • 0 in reply to Josh Wyatt
    Prodigy 75 points

    John,

    Does a binary file need to be treated in a different way?

    Mike

  • 0 in reply to Mike Unger
    TI__Guru* 91206 points

    Dear Mike - 

    I was pointing out the direction of the separators in directory structure (the forward slashes)

  • +1 in reply to Josh Wyatt
    Prodigy 75 points

    John,

    I know you were. I was trying to get you to answer my question if binary files need to be treated differently. :) 

    It would seem not, that there is no extra parameter that needs to be added to the --file line.

    Anyway, I've got it to work but I don't know why. Here is my .cfg file:


    # First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
    --flash-writer=../../../../release/SBL_UART_UNIFLASH.tiimage

    # Now send the PPAR binary to flash

    --file=../../../release/ppar.bin --operation=flash --flash-offset=0x1F0000

    The two files are in the same directory, so why I have to specify one at a different nesting level is beyond me but ... it seems to work.

    Mike

  • 0 in reply to Mike Unger
    TI__Guru* 91206 points

    Dear Mike -

    I'm glad you solved your issue, thanks for letting us know. 

  • 0 in reply to Josh Wyatt
    Prodigy 75 points

    Yep, just don't quite understand but whatever.
    Josh, so sorry I've been calling you John throughout this thread. I'm nuts. I'll blame it on the white on yellow font. Slight smile

    Mike