AWRL6844EVM: FLASH erasure and writing errors

Part Number: AWRL6844EVM
Other Parts Discussed in Thread: SYSCONFIG, MMWAVE-L-SDK, AWRL6844,

Tool/software:

environment:

  • SysConfig 1.23.0
  • TI CLANG Compiler 4.0.2.LTS
  • Python 3.x (with required packages)
  • CCS 20.1.0 (for CCS builds)
  • xWRL684x MMWAVE-L-SDK  06.00.04

demo program:

C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_InCabin_Security_and_Safety\AWRL6844_InCabin_Demos

Based on the demo program, add the following code to the demo_in_cabin_sensing_6844_mss function. (Please refer to the attached figure for the code.):

Parameter description:

1."readData" is used to read the results after erasure.

2."writeData" represents the value to be written to the flash memory.

3."readData2" is used to read the values stored in the flash memory.

test result:

The result of the read and erase operation is not 0xFF. The write and read functions throw an exception code of -2. The read value is inconsistent, and sometimes a fixed value of 0xCC is read out.

  • Hi,

    One of our SW experts will get back to you in a day or two.

  • Hi,

    -2 Refers to timeout error, it could be possible that the Flash is busy with erase operation, could you check by adding a delay between each of the API's and test again.

    Please add a delay in the order of few seconds, just to be safe.

    Regards,

    Ajay

  • Hi Ajay,

    Last time, the function in the red box was forgotten to read and return the value. This time, it has been added and a 5-second delay has been included. However, the write function still throws exception -2. Since I have been testing with the AWRL6844EVM board and the demo routine (C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_InCabin_Security_and_Safety\AWRL6844_InCabin_Demos), only adding the code shown in my screenshot, I would like to know if your test results are the same as mine. I used the routine C:\ti\MMWAVE_L_SDK_06_00_04_01\mmwave_l_sdk_06_00_04_01\examples\drivers\qspi\qspi_flash_transfer, and the flash can be erased, writte, and read normally. However, we are currently conducting research and development using the AWRL6844_InCabin_Demos project. Therefore, I want to solve this problem. Would you be willing to test it and check if the flash can be read and written normally?

    code modification:

    test result:

  • Hi tengyuan,

    Let me test it at my end and get back to you by Wednesday.

    Regards,

    Ajay