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.

AWR1642: How to use GEL file instead of flashing ccs_debug.bin on QSPI Flash?

Part Number: AWR1642
Other Parts Discussed in Thread: MMWAVE-STUDIO,

Hi team,

Customer had design it's own AWR1642 board, but they miss the QSPI flash when layout. 

For debug purpose, Is it possiable to use GEL file instead of flashing ccs_debug.bin on QSPI Flash? And how to do it?

Thanks.

Regards,

Wesley

  • Hi Wesley,
    Let me check and get back to you.

    Regards,
    Jitendra
  • Hi Wesley,
    AWR1642 bootloader supports load over SPI. If AWR1642 bootloader doesn't detect sFlash connected to it then it switched to SPI interface looking for MetaImage file (application image).
    But this image shouldn't have 4 bytes CRC at the end which requires for flash mode only whereas SPI download user needs to remove CRC part at the end of MetaImage application file.
    And to download this MetaImage over SPI you can use mmWave-Studio.
    1. Set Device in functional mode (only jumper on SOP0).
    2. SPI connect from mmWave Studio.
    3. Select above MetaImage.bin from 'BSS FW' field and click load.

    Steps to generate MetaImage without CRC (4Bytes) at the end of the binary

    1. From CCS project: MSS app CCS project properties->Build->Steps,  remove last post-build steps containing command '{COM_TI_MMWAVE_SDK_INSTALL_DIR}/packages/scripts/ImageCreator/append_bin_crc/gen_bincrc32.exe ' and build the MSS application.

    2. From gmake build: edit package\scripts\windows\generateMetaImage.bat, comment 'call %CRC_EXE% %FLASHIMAGE%' line in this file.



    Regards,
    Jitendra

  • Hi Jitendra,

    Thanks for your reply.

    I had follow your step, but the BSS FW load can not be load from SPI.

    I had attach the output information below, could you please help to point out how to do it using mmwave studio? which software version is working for this method?

    i cannot connect to device using SPI connect. Also, the FW download can not be used in functional mode.

    Thanks.

    GM: Constructor
    GM: Mon Feb 25 16:37:45 2019
    RSTD.Transmit("/Settings")
    [16:37:46]  
    [16:37:46]  ### Running Startup script: "C:\ti\mmwave_studio_01_00_00_00\mmWaveStudio\Scripts\Startup.lua" ###
    [16:37:46]  RSTD.SetAndTransmit ("/Settings/Scripter/Display DateTime" , "1")
    [16:37:46]  RSTD.SetAndTransmit ("/Settings/Scripter/DateTime Format" , "HH:mm:ss")
    [16:37:46]  Scripter ignored: Attempt to UnBuild() again or before Build.
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 0/Dll" , "C:\\ti\\mmwave_studio_01_00_00_00\\mmWaveStudio\\Clients\\\\LabClient.dll")
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 0/Use" , "TRUE")
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 1/Use" , "FALSE")
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 2/Use" , "FALSE")
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 3/Use" , "FALSE")
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 4/Use" , "FALSE")
    [16:37:46]  RSTD.SetVar ("/Settings/AL Client/AL Dll" , "C:\\ti\\mmwave_studio_01_00_00_00\\mmWaveStudio\\RunTime\\SAL.dll")
    [16:37:46]  RSTD.SetVar ("/Settings/Clients/Client 0/GuiDll" , "")
    [16:37:46]  RSTD.SetVar ("/Settings/AutoUpdate/Enabled" , "TRUE")
    [16:37:46]  RSTD.SetVar ("/Settings/AutoUpdate/Interval" , "1")
    [16:37:46]  RSTD.SetVar ("/Settings/Monitors/UpdateDisplay" , "TRUE")
    [16:37:46]  RSTD.SetVar ("/Settings/Monitors/OneClickStart" , "TRUE")
    [16:37:46]  RSTD.SetVar ("/Settings/Automation/Automation Mode" , "false")
    [16:37:46]  RSTD.Transmit("/")
    [16:37:46]  RSTD.SaveSettings(): Settings saved to "C:\Users\AppData\Roaming\RSTD\config.xml"
    [16:37:46]  RSTD.Build()
    [16:37:46]  RSTD.SaveSettings(): Settings saved to "C:\Users\AppData\Roaming\RSTD\config.xml"
    [16:37:46]  RSTD.Transmit("/")
    [16:37:46]  RSTD.AL_Build()
    [16:37:46]  RSTD.AL_LoadXml()
    [16:37:46]  RSTD.Transmit("/")
    [16:37:46]  RSTD.AL_Init()
    [16:37:46]  RSTD.Clients_Build()
    [16:37:46]  GM: Init
    [16:37:46]  GM: Loaded 'C:\ti\mmwave_studio_01_00_00_00\mmWaveStudio\Clients\\LabClient.dll'
    [16:37:46]  GM: 1 Guest (s) init
    [16:37:46]  GM: 1 Module(s) init
    [16:37:46]  GM: 2 Tab   (s) init
    [16:37:46]  RSTD.Client_LoadXml()
    [16:37:47]  [RadarAPI]: Starting Matlab Engine..
    [16:37:53]  [RadarAPI]: Matlab Engine Started!
    [16:37:56]  [RadarAPI]: ar1.LoadSettings('C:\Users\AppData\Roaming\RSTD\ar1gui.ini')
    [16:37:57]  TESTING = false
    [16:37:57]  
    [16:37:57]  ***Script completed successfully.***
    [16:38:15]  [RadarAPI]: Opening Gpio Control Port()
    [16:38:15]  [RadarAPI]: Status: Passed
    [16:38:15]  [RadarAPI]: Opening Board Control Port()
    [16:38:15]  [RadarAPI]: Status: Passed
    [16:38:16]  [RadarAPI]: ar1.FullReset()
    [16:38:16]  [RadarAPI]: Status: Passed
    [16:38:17]  [RadarAPI]: Closing Board Control Port()
    [16:38:17]  [RadarAPI]: Status: Passed
    [16:38:17]  [RadarAPI]: Closing Gpio Control Port()
    [16:38:17]  [RadarAPI]: Status: Passed
    [16:38:17]  [RadarAPI]: ar1.SOPControl(4)
    [16:38:17]  [RadarAPI]: Status: Passed
    [16:38:18]  [RadarAPI]: ar1.Connect(5,921600,1000)
    [16:38:20]  [RadarAPI]: Warning: Connected with baudrate 115200
    [16:38:21]  [RadarAPI]: Warning: Disconnected existing BaudRate
    [16:38:22]  [RadarAPI]: Warning: Trying to connect with baudrate 921600
    [16:38:23]  [RadarAPI]: ar1.Calling_IsConnected()
    [16:38:24]  [RadarAPI]: ar1.SelectChipVersion("XWR1642")
    [16:38:24]  [RadarAPI]: Status: Passed
    [16:38:25]  [RadarAPI]: ar1.SelectChipVersion("XWR1642")
    [16:38:25]  [RadarAPI]: Status: Passed
    [16:38:25]  [RadarAPI]: ar1.SaveSettings('C:\Users\AppData\Roaming\RSTD\ar1gui.ini')
    [16:38:31]  [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
    [16:38:31]  Status: Failed, Error Type: RESP TIMEOUT
    [16:38:31]  [RadarAPI]: ar1.SaveSettings('C:\Users\AppData\Roaming\RSTD\ar1gui.ini')
    [16:38:34]  [RadarAPI]: Download over RS232 is not supported in Functional Mode!
    

  • Hi Wesley,
    Make sure that device is set in functional mode (SOP0 jumper only). [I assume you have it already]
    And from mmWave Studio
    1. Reset control.
    2. Don't connect over RS232 (skip RS232 operations button).
    3. Click SPI Connect.
    4. Load MetaImage (without CRC at end of binary) from 'BSS FW' input field.

    This way it worked with me. Please try and let me know it this solves your issue.

    Regards,
    Jitendra
  • Hi Jitendra,

    I had test it again, but the SPI connect fail. Then the FW load failed again. The output information is listed below:

    The software version is mmwave_studio_02_00_00_02. Are you using different version of mmwave studio?

    Thanks.

    [17:32:14] TESTING = false
    [17:32:14]
    [17:32:14] ***Script completed successfully.***
    [17:32:19] [RadarAPI]: Opening Gpio Control Port()
    [17:32:19] [RadarAPI]: Status: Passed
    [17:32:20] [RadarAPI]: Opening Board Control Port()
    [17:32:20] [RadarAPI]: Status: Passed
    [17:32:21] [RadarAPI]: ar1.FullReset()
    [17:32:21] [RadarAPI]: Status: Passed
    [17:32:21] [RadarAPI]: Closing Board Control Port()
    [17:32:21] [RadarAPI]: Status: Passed
    [17:32:21] [RadarAPI]: Closing Gpio Control Port()
    [17:32:21] [RadarAPI]: Status: Passed
    [17:32:21] [RadarAPI]: ar1.SOPControl(2)
    [17:32:21] [RadarAPI]: Status: Passed
    [17:32:31] [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
    [17:32:31] Status: Failed, Error Type: RESP TIMEOUT
    [17:32:34] [RadarAPI]: ar1.DownloadBSSFw("C:\\Users\\Desktop\\xwr16xx_mmw_demo_test.bin")
    [17:32:34] [RadarAPI]: Error: Download FW failed with error -1

  • Hi Jitendra,

    I had try both 1243, 1443 and 1642 platform.
    Only 1243 works in this way. 1443 and 1642 can not load image using this way. It fails on SPI connect.

    Could you please double check with the AWR1642?
    Thanks.
  • If you are trying with AWR1642BOOST EVM then you need to remove sFlash connection with AWR1642 silicon, so that on power on device's bootloader doesn't detect any sFlash connected with device and switches to SPI boot mode.

    With default EVM you will not able to connect over SPI till you disconnect sFlash device.

    Regards,
    Jitendra
  • It works. Thanks for your great support.