AWR2944EVM: Uniflash gets stuck in the state of initalization complete or Flash.

Latest situation, it fails at the middle of the process of flashing.

How to deal with this problem.

Hi Zisheng,

Are you using an EVM or your own board? The voltage should be pulled up to 3.3, so if you are not reading 3.3 at the pull up, there might be a damage. 

Have you checked the voltages if there are correct on the board? as well as VBGAP if its there. 

Regards,

Aydin

Hi Aydin

We now ensure the voltage of SOP4 is 3.3V, and the process of flashing will not get stuck in state of initalization complete or flashing. 

It can start flashing, but will fail in the middle of the process as seen below.

Regards,

Zisheng Wang.

Hi Zisheng,

That's good to hear the board is fine. 

• Before loading the image, remove the XDS_USB then the power supply from the board. 
• Connect the power supply, wait 4-5 seconds then connect the XDS USB. 
• Please double check the COM port from the device manager (XDS110/User UART (COMXX).
• If still having issues, could you let us know the SBL image and App Image you are using

Regards,

Aydin

Hi Aydin,

I am sorry to forget to provide the information that I changed the flash used by the board.

I find it availiable to use MX25V1635F on the AWR2944, are there some settings need to be modified to make it work?

Regards,

Zisheng Wang 

Hi Aydin

Which interface should I use? I don't find it.

Regards,

Zisheng  Wang

Hi Aydin

The figures above is my code generated by sysconfig in project sbl_qspi.

As shown above, Flash_Open fucntino will call Flash_norQspiSetQeBit based on the protocol which is 1S_1S_4S and the QE bit is 1.

Doesn't it mean that QE bit is already set?

Regards,

Zisheng Wang

Hi Aydin

I follow the solution of flashing in the user guide, building three project, sbl_uniflash, sbl_qspi,out_of_box_2944 in which I modify flash config into mx25V1635F through sysconfig.

Then I use python to flash, it still can't work.

Error information is below.

Is there anything else I forget to do?

Regards,

Zisheng Wang

Hi Zisheng,

This would be a question to the vendor or our SW team, but they're out of office until next week due to holidays. There is a similar thread that the software team responded AWR2944: How to add MX25V1635F flash for TI AWR2944 - Sensors forum - Sensors - TI E2E support forums 

Regards,

Aydin

Hi Aydin

After inquiring solution in it. One thing I don't understand that it is said that what is the commands in the solution of  "populate all the commands and fields of it in the syscfg properly." 

Aydin Kiasat said:

 AWR2944: How to add MX25V1635F flash for TI AWR2944 - Sensors forum - Sensors - TI E2E support forums 

Regards,

Zisheng Wang

Hi Aydin,

I have look through the data sheet of the flash, but there stall are some field in the sysconfig not found, as a result, my board  still can't work.

So I want to ask you if you have a successful version of  config of flash in sysconfig  which can work.

Regards,

Zisheng Wang

Hi Aydin,

I brought some flash as same model as  flash of demo, but there are some weird problems.

1.it can flash, but the program can't execute.

2.the device ID of flash of demo, GD25B64C,  is 0x4017 in the code, but I google it , find it is 0x4016. In the data sheet of flash of demo, there is a weird description about Device ID as figure below.These commands all look up device ID, but the result is different.

Figures below are flash of demo(up) and I brought(down).

Model is same, but there is something different.Is this the problem why the program can't work?

Regards,

Zisheng Wang

Hi Zisheng, 

I've requested our SW team to guide on the code modification. In the meantime, please refer to similar threads on E2E, AWR2944: Unable to flash using UNIFLASH - Sensors forum - Sensors - TI E2E support forums

AWR2944: The chip model of the FLASH was changed, but the program failed to be written - Sensors forum - Sensors - TI E2E support forums

Regards,

Aydin 

Hi Aydin,

Aydin Kiasat said:

AWR2944: The chip model of the FLASH was changed, but the program failed to be written - Sensors forum - Sensors - TI E2E support forums

I follow this solution and changed flash into MX25V1635F, and modified the config in sysconfig.

It can flash, but get a error of flash verifying.

I checked the code in sbl_uart, found that the reason cause the error is that there is difference between file received from PC and read from flash into which sbl_uart write file received.

So it is a problem about flash hardware?

I am looking forward to your assistance.

Regards,

Zisheng Wang.

Hi Zisheng,

I don't think there is hardware issue here if you are using the TI EVM board. Please refer to the following similar thread AWR2944: UNIFLASH GD25Q64C flash verify failed! - Sensors forum - Sensors - TI E2E support forums

Regards,

Aydin 

Hi Aydin,

Ok, I get it.

By the way, need I change the base address of flash which is 0xC0000000 in AWR1843 different from GD25B64C in AWR2944.

Regards, 

Zishing Wang

Hi Zisheng,

I'm passing this thread over to the SW team for further help on the code modification. An expert from the SW team will respond shortly.

Regards,

Aydin 

Hi Zisheng,

Can you clarify which modification you are referring here to? You can use the uniflash tool to flash the images in 1843 device, it expects the images from location 0xc0000000.

Regards,

Shruti

Hi Shruti,

I mean the base address in command passed to flash.

It is 0xC6000000 for GD25B64C in AWR2944, 0xC0000000 for MX25V1635F in AWR1843,  should I modify it into 0xC0000000 when using MX25V1635F on  the board of AWR2944.

Regards,

Zisheng Wang

Hi shruti,

I find that there is a way to use custom flash on the board in user guide of sdk.

It can make sense to use qspi_flash_diag to query information of flash.

But when I flash it into board by uniflash, an error occurs.

It happens during flashing, what is wired is sbl_qspi can be flashed, but it will fail when it comes to ccs_debug.

I really need your help, this problem has been so long.

Regards,

Zisheng Wang

Hi Zisheng,

Please recheck the following sequence if you have missed anything - 

1. Solder the new Flash variant into your board.

2. Run the sbl_qspi_diag.appimage which is present in the mcu_plus_sdk_<device>_<version>/drivers/examples/qspi , on execution there will be output generated on the console. Copy and save the following data in a .json file.

3. Then it is necessary to change the all the appimage and tiimage with the new flash setting. 

4. Open the sysconfig tool and within that go to board section, there is a flash option, there In Flash Device, select custom flash option and in flash name provide the name of the version that you are using.

5. Then add the .json file created in previous step to following configuration.

6. In case the above file doesn't works, then add the given indicators using the datasheet of the device. The important indicators that need to be looked upon are Flash JEDEC Manufacturer ID, Flash JEDEC Device ID, Flash Size in Bytes, Quad Enable Type, Reset Type etc. These indicators can vary according to flash variants.

7. Then build all the appimage and tiimage with new configuration.

8. Flash the sbl and appimage in uniflash.

Please check if you have followed the same sequence as mentioned above.

Regards,

Shruti

Hi Shruti,

I don't know how to do this.

shruti gupta said:

2. Run the sbl_qspi_diag.appimage which is present in the mcu_plus_sdk_<device>_<version>/drivers/examples/qspi , on execution there will be output generated on the console. Copy and save the following data in a .json file.

I look up the sbl_qspi_diag in the SDK docs.

Is it this?

It shows that I need to use CCS to execute it, but when I see what in it, it needs flash:

When I followed the guide, I get the error informatino like this:

This code is called because of failure of Flash_open.

So the situaion is I need flash to execute the sbl_qspi_diag, but the configuration of flash I need requires the result of execution of sbl_qspi_diag.

It sounds funny, right?

How to execute sbl_qspi_diag?

Help me,please. I have had no idea but your assistance.

Regards,

Zisheng Wang.

Hi Zisheng,

Have you gone through the following documentation - 

AWR294x MCU+ SDK: Adding Support For a Custom Flash Device

If not, then I would suggest you to go over this document first.

for this query - 

紫圣 王 said:

So the situaion is I need flash to execute the sbl_qspi_diag, but the configuration of flash I need requires the result of execution of sbl_qspi_diag.

This is a diagnostic example for NOR-QSPI Flashes. This example doesn't use the flash driver and should ideally pass for any NOR-QSPI flash.

Regards,

Shruti