AWR2E44PEVM: Can notflash AWR 2X44

Part Number: AWR2E44PEVM
Other Parts Discussed in Thread: UNIFLASH, , AWR2E44

Tool/software:

Hi 

I am trying to flash  .cfg  without success but in previous time it did flash without any problem 

python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/awr2x44p-evm/default_sbl_null.cfg

  

Regard

Raz Koren 

  • I have the same problem, but this hardware has never worked for me. I am currently working with an older version of the hardware, where flashing the SBL was not a problem. To be precise, it does not work with version AWR2E44PEVM, but it does work with version AWR2E44 LOP EVM.

  • Hello,

    First please make sure to only connect to XDS_USB port. Not the FTDI port.

    Second, make sure you have a 12V and approx 2.5A power supply.

    To continue can you please send a picture of your setup? I want to verify the SOP switches are in a correct mode.

    We'll continue from here.

    Best,

    Gabriel

  • Hello 

    It was working with 5V, 3A  , It was checked with other TI engineers 

    Suddenly it is not working , and i use the same power supply 

    The SOP are in flashing mode , 1 0 1 as in the manual and i succeeded to flash in this mode previously 

    Other people wrote that they replace the board and it solve the problem 

    Regards

    Raz Koren 

  • Hello Gabriel,

    Thanks for your quick reply. Here are the pictures you requested...

          

    Best Regards,

    Andreas

  • Hi 

    I will also test it with 12V 2.5A and will inform you if it was solved 

    Regards

    Raz Koren 

  • Hello,

    I don't understand what you mean by "Suddenly not working." Can you give a better explanation on what happened. Did you unplug something? What were you able to flash before? Have you tried just flashing the OOB demo?

    Also in the command line did you run the setenv.bat file present in the following path?

    "C:\ti\mmwave_mcuplus_sdk_04_07_01_03\mmwave_mcuplus_sdk_04_07_01_03\scripts\windows\setenv.bat"

    Also please refer to the "4.2.4. Flash Procedure using Python tools" section in the user guide in the SDK. It highlights the steps to use for flashing.

    Please try flashing the whatever is in default.cfg first and let me know if there are any issues. The following path is where default.cfg is.

    C:\ti\mmwave_mcuplus_sdk_04_07_01_03\mmwave_mcuplus_sdk_04_07_01_03\tools\awr2x44P

    Best,

    Gabriel

  • Hi 

    Yes i run setenv.bat before , ( i just power on/off  to determine flashing mode , i succeeded to do step 2(flash) as  in the file attached below   

    please see the attach file which explain all the steps that i did for flashing  

    if you want i can also send you screen shoot of each step or a video with all the steps as you wish 

    CCS.docx

    Regards

    Raz Koren 

  • Hi 

    this doc shows all the step that i did ' the command of flash using python still does not allow to flash , after writing the command it show the following respond  

  • Hello,

    I managed to flash the same exact .cfg that was giving you issues so I will provide my exact steps to help you reproduce

    Note* Ensure to power cycle the board before every flash attempt.

    1) Run setenv.bat, make sure that MMWAVE_SDK_DEVICE is set to awr2x44p

    2) Next in terminal navigate to the following path in the SDK. From there edit the .cfg file to fix the file paths. I have also just attacked the one I used if that is easier

    C:\ti\mmwave_mcuplus_sdk_04_07_01_03\mcu_plus_sdk_awr2x44p_10_01_00_04\tools\boot\sbl_prebuilt\awr2x44p-evm\

    default_sbl_null.cfg

    3) Next run the python command

    python C:\ti\mmwave_mcuplus_sdk_04_07_01_03\mcu_plus_sdk_awr2x44p_10_01_00_04\tools\boot\uart_uniflash.py -p COM33 --cfg=default_sbl_null.cfg

    The flashing should be successful. Again make sure to restart the board (by unplugging its power source) and then try to flash. 

    Best,

    Gabriel

  • Hi

    After changing power supply , here are the results 

    Trying to falsh default.docx

    I think it better to check the hardware , maybe the flash or maybe something else 

    I don't have the knowledge of a TI developer of this AWR2X44 board 

    Regards

    Raz Koren 

  • I figured out what the problem was, now I can work on it. The crypto part is active on my chip and I can only write signed images to the flash memory. The sample images provided in the SDK are not signed and are therefore rejected by the bootloader.

  • Hello,

    I am glad this issue was resolved. I will be closing this thread and any future questions please start a new one. 

    Best,

    Gabriel