• State Resolved
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 82 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AWRL6844: how to use arprog_cmdline_6844.exe?

Albert Yip
Prodigy 210 points

Part Number: AWRL6844

I have found the tool named "arprog_cmdline_6844.exe" in your SDK, I know it can download the appimage into the flash, but I don't know how dose it verify the address where the appimage will be downloaded. And how much space will it erase? 

  • 0
    TI__Genius 16466 points

    Hey Albert,

    Thanks for reaching out regarding the standalone flashing tool. I would recommend taking a look through the SDK documentation for the aprog_cmdline_6844.exe tool under <MMWAVE_LSDK_INSTALL_DIR>/tools/FlashingTool/Readme_arprog_cmdline_6844.html. 

    The address where each image is downloaded is specified through the -ofN argument followed by the address offset in SFLASH where N represents the index of which appimage is to be stored in SFLASH. 

    The tool does not erase the SFLASH unless the -fr argument is provided which will then erase the entire SFLASH.

    Hopefully these initial answers help, but feel free to take a look through the documentation for additional information.

    Cheers,

    Kristien

  • 0 in reply to Kristien Everett
    Prodigy 210 points

    What's the SFLASH? the external flash? Does not erase? But as I know, a flash block or sector must be erased before being written, right?

    the -ofN argument is optional, what's the download address if I don't specify the -ofN argument?

  • +1 in reply to Albert Yip
    TI__Genius 16466 points

    Hey Albert,

    Sorry for the confusion. Yes, the SFLASH is the external flash that appimages are stored in. You are correct that when writing to the SFLASH, the sector or block should be erased before being written to. The arprog_cmdline tool handles this automatically when flashing an appimage as it will erase the minimum sectors or blocks needed before writing the appimage. 

    Just to reiterate, the -fr argument is for erasing the entire SFLASH whereas the default behavior of the tool will be to erase and write over only the sectors needed for an appimage.

    If no offset is given, then the tool will place appimages sequentially and aligned to 4 KB boundaries starting at address 0x00002000 of the SFLASH. For example, if you had two appimages, Image A (Size: 255KB) and Image B (96KB), Image A will start at 0x00002000 and Image B will start at 0x000420000. Note: The first 8KB of SFLASH is always reserved for the flash header sector and backup flash header sector.

    Hopefully this helps, but let us know if you have any other questions.

    Cheers,

    Kristien