AWR2944EVM: trouble completing the EVM setup for AWR2944EVM.

Part Number: AWR2944EVM
Other Parts Discussed in Thread: UNIFLASH

SDK Used: mcu_plus_sdk_awr294x_10_01_00_04.

 
I am currently at this stage : "Flash SOC Initialization Binary"
Now, here, I did the setup of EVM in UART Boot mode as mentioned and observed the character 'c' printed in CCS terminal window. 
I closed this ccs terminal window and then ran the boot script mentioned: 
  python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/awr294x-evm/default_sbl_null.cfg
 
In this stage my build process is failing. Could you kindly help me here, below is the snippet of the error message I am seeing:
Image preview 
  • Hi Srikar,

     It seems the image did not come through. Could you please reattach the image or share it again?

    Regards,

    Ananya K C

  • Hello Ananya,

    Here you go, I also forwarded it to Hakan via email before.

  • Hello Srikar,

    Could you please check the following:

    • Ensure that UART boot mode is enabled and that the board is reset using the NRST pin before starting the flashing process.
    • Confirm the serial flash part number — are you using the default flash part provided with the EVM?
    • If you have made any modifications to the SBL code, please make sure to rebuild the application before flashing.

    Regards,

    Ananya K C

  • Hi Ananya,

    Sorry for the late response, I did perform what you mentioned

    Ensure that UART boot mode is enabled

    By this statement I am assuming you mean to short J17 and J20, yes, I did the setup as 101 respectively.

    the board is reset using the NRST pin

    I did use the NRST to reset before flashing.

    Confirm the serial flash part numbe

    Serial Number: 08251940347.

    are you using the default flash part provided with the EVM?

    Can you elaborate more on what do you mean by default flash part?

    If you have made any modifications to the SBL code, please make sure to rebuild the application before flashing.

    No modifications made yet. I am trying to flash the default scripts only for now.

  • Hi Srikar,

    Did you try flashing the board multiple times after power cycling the board. Are you getting the same response every time?

    This is a list of issues and possible solutions:

    Could you try flashing another cfg file given in this command?

    python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/awr294x-evm/default_sbl_qspi.cfg

    Regards,
    Ananya K C


  • Did you try flashing the board multiple times after power cycling the board. Are you getting the same response every time?

    Yes, I did try multiple times now and still see this error coming up, I also tried to reboot the EVM by pressing NRST button before flashing but still see this issue. 

    python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/awr294x-evm/default_sbl_qspi.cfg

    I tried to look into the cfg file in this command and found that the appimage mentioned in this cfg is not part of the sdk folder. Should i get from elsewhere? highlighted in the below image is the file I'm not seeing in the sdk structure.

  • Hi Srikar,

     You have to build the project to obtain the hello_world.release.image. 

    The steps to build the project is given in: AWR294x MCU+ SDK: Build a Hello World example under the section "Using Makefiles". The only change to be made in the gmake command is to change the path from "examples/hello_world/{board}/r5fss0-0_freertos/ti-arm-clang" to "examples/hello_world/awr294x-evm/r5fss0-0_nortos/ti-arm-clang".

    Once the image is built you can flash it using the same cfg file.

    Another change you can try is to change the second command to "--file=sbl_prebuilt/awr294x-evm/sbl_qspi.debug.tiimage --operation=flash --flash-offset=0x0" and check if you are able to flash the sbl successfully. The change is sbl_qspi.release.tiimage is changed to sbl_qspi.debug.tiimage.

    Regards,

    Ananya K C

  • Hi Ananya,

    I've tried the two commands you suggested, and I see errors for both of the commands, please also note that i rebooted the EVM before performing any of the following actions:

    for the first command: 

    1. I did build the hello world image and then tried to flash the default_sbl_qspi.cfg.

    2. for the second command I ran the command now by changing the second file to debug_tiimage and received the following error:

  • Hi Srikar,

    Could you please confirm whether the JTAG MUX on the board is currently pointing to XDS? Attached below is the picture pointing to the part on the EVM.

    Can you try to flash the firmware using UniFlash and let me know whether the same issue occurs. To download UniFlash the link is present in this path "AWR294x MCU+ SDK: Download, Install and Setup SDK and Tools". Below are the steps to follow:

    1. Download UniFlash

      • The download link is present in the page provided above.
    2. Install UniFlash (if not already installed) and launch the application.

    3. Load the Images

      • In the UniFlash GUI, load the SBL (Secondary Boot Loader) into the designated slot.
      • Load the application image(s) into their respective slots.
    4. Configure the COM Port

      • Select the correct COM port that corresponds to the board’s UART connection.
    5. Flash the Images

      • Monitor the progress and verify that the operation completes without errors.

    After completing these, please let me know:

    • Whether the JTAG MUX is set to XDS.
    • If the flashing succeeds or if the same problem persists while using UniFlash.
    • Any error messages or logs that appear during the process.

    Regards,

    Ananya K C

  • Hi Ananya,

    I have the JTAG MUX in XDS mode. I did try loading the images through uniflash:

    below are the images being flashed:

    below are the COM ports read:

    I also tried the similar procedure with COM44, but I still get the same error as well. 

  • Hello Srikar,

     Could you try flashing the sbl_qspi image. Are you getting the same error? 

    Did you try changing the interfacing the PC and EVM? Also, when you are flashing the images are the ports being used by any other application.

    Regards,

    Ananya K C

  •  Could you try flashing the sbl_qspi image. Are you getting the same error? 

    I tried all the following experiments and still see the same error, note that I did power recycle before performing each of the following flashes:

    In Boot Mode:

    1. I tried with sbl_qspi.release and hello_world.release

    2. sbl_qspi.release and hello_world.qspi.release

    In QSPI mode:

    1. sbl_qspi.release and hello_world.release

    2. sbl_qspi.release and hello_world.qspi.release

    Did you try changing the interfacing the PC and EVM?

    If by this you mean to change the USB port used to connect to PC: then yes, I did change the USB port used to connect to the PC.

    Also, when you are flashing the images are the ports being used by any other application.

    No, the ports are not being used by other applications. Uniflash is the only app that is accessing them at the moment of flashing. 

  • Hi Srikar,

     Then can you try a few simple experiments:

    1. In UART mode (when SOP2 and SOP0 are shorted and SOP1 is open) while connected to XDS110 Class Application/User UART to a serial monitor can you press the nRESET button on the EVM and post the screen shot.

    2. The same experiment but in functional mode (when SOP0 is shorted and SOP1 and SOP2 is open) and post the screen shot.

    Thank you for your patience.

    Regards,

    Ananya K C

  • Below are the ports as they are recognized:

    In UART mode (when SOP2 and SOP0 are shorted and SOP1 is open) while connected to XDS110 Class Application/User UART to a serial monitor can you press the nRESET button on the EVM and post the screen shot.

    2. The same experiment but in functional mode (when SOP0 is shorted and SOP1 and SOP2 is open) and post the screen shot.

  • Hi Srikar,

     Thank you for the reply. I will get back to you in two days. Thank you for your patience.

    Regards,

    Ananya K C

  • Hi Srikar,
     Section 3.3.2 of the mmwave_mcuplus_sdk_user_guide describes how to load the .appimage onto the board using Code Composer Studio. Could you review the steps and verify whether you are able to connect to both the R5 core and the D66x core?

    Regards,

    Ananya K C

  • Hello Ananya,

    Yes, I am able to connect to R5 and C66x_DSP core in CCS:

    But i couldn't find the programs that are asked to be loaded into the respective cores, when I right click on the core I couldn't find the load program option as mentioned within the user guide:

    Rather I kept the core in running mode and then through the run dropdown from toolbar on the top of CCS, I found load program. However, when i navigate to the location mentioned in user guide where the files to be loaded are present:

    although these files are present in my sdk, I'm not able to load them onto CCS via navigation after "Load Program" option is selected:

    this is the location where the files are presented, but I am not finding them when I navigate from Load program option. 

    Also, please note that the issue with uart_uniflash.py with default.cfg which was initially described in this thread. Running that file is also part of this setup procedure itself and this step was not successful again. 

  • Hi Srikar,

     You can view the files by changing to "All files" when loading the files to respective cores.

    Regards,

    Ananya K C

  • Hello Ananya,

    Thanks for the input. I was able to load the programs into respective cores as mentioned in the user guide. 

    However, to proceed further into Running the Demos section, as mentioned in the guide I need to be able to flash the .appimage successfully which is not possible since the error is not rectified yet.  

    Let me know your thoughts.

    Thank you.

  • Hello Srikar,

     This experiment was to test if the JTAG is working. Since it is working you can use JTAG Flasher script present in the Radar Toolbox. I have attached the link for your reference: JTAG Flasher 

    You can download Radar Toolbox and locate the JTAG Flasher folder and run the script for 2944. Please follow the JTAG Flasher User Guide present in the docs folder.

    Through this method you will be able to flash the appimage.

    Regards,

    Ananya K C