• State Resolved
  • Locked Locked
  • Replies 22 replies
  • Answers 7 answers
  • Subscribers 35 subscribers
  • Views 1122 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

IWRL6432: System topology

IWRL6432: Flash Memory for 1.8V operation

poolplayer
Prodigy 120 points
Part Number: IWRL6432
Other Parts Discussed in Thread: IWR6843, SYSCONFIG

I want to use IWRL6432 with I/O 1.8V, but the voltage specification of MX25V1635F is 2.3V-3.3V. Could you introduce me to a flash memory that operates at 1.8V?

  • 0
    TI__Genius 14415 points

    Please see the following document. It details other supported flash memory chips. Please note that it states IWR6843, but the interface is the same as the IWRL6432. There is a similar macronix flash that is for 1.9 or wide Vin.

    https://www.ti.com/lit/an/sprach9d/sprach9d.pdf

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 120 points

    Hi Thomas-san
    I replaced the flash memory with the MX25R1635F listed in this document and tried to write the FW, but it didn't work. In the release notes of SDK5.3, there is no description that flash memory other than MX25V1635F can be used, but is it really supported?

  • 0 in reply to poolplayer
    TI__Genius 14415 points

    Hello,

    You will need to modify sysconfig to change the part number to enable that flash device. If you open the sysconfig file inside of CCS you should be able to modify the flash section. Most of the parameters should be the same, but you will need to change them to match the part number above. Then you will need to rebuild the project.

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 120 points

    Hi Thomas-san
    I will try following your advice.
    thank you.

  • 0
    Prodigy 220 points

    Hi Thomas-san

    We have attempted to follow the steps outlined in the "Adding Support For a Custom Flash Device" section of the README_FIRST_xWRL6432.html of SDK5.3 in order to replace the flash memory with the MX25R1635F. However, we encountered an error message stating "QSPI read data mismatch!!!" during "QSPI Flash Diag". Do you have any idea about the possible cause for this error?

    Furthermore, we also attempted to load a json file in the Flash configuration of SysConfig, but it seems to be stuck at "Running external process...". Can you provide any insights into the possible cause of this issue?

    Regards

  • 0 in reply to ryo.sugiura
    TI__Mastermind 19560 points

    Hello.

    We are forwarding this to the appropriate team member.  Please allow them some time to respond.

  • 0 in reply to Santosh Krishnan
    TI__Genius 9680 points

    Hi,

    You can use the MX25R1635FZUIH0 Flash memory. Its wide input 1.65V-3.6V, so you can operate it both 1.8V & 3.3V.

    The "QSPI read data mismatch" could occur as a result of a data mismatch between the data being written and read. "QSPI Read Diag" is an example code. If you could specify precisely where the example code failed, I'd be able to comment more.

    I am attaching snapshots of steps to generate a new build of appimage that should support the MX25R1635F flash memory and the generated appimage file.

    1. Open sysconfig tool using the command. 

    • gmake -s -C examples/mmw_demo/motion_and_presence_detection/xwrL64xx-evm/m4fss0-0_freertos/ti-arm-clang syscfg-gui

    2. Change the device ID to 2815 for MX25R1635F. And save the SYSCONFIG file.

     

    3. Clean & generate new appimage using below commands.

    • gmake -s -C examples/mmw_demo/motion_and_presence_detection/xwrL64xx-evm/m4fss0-0_freertos/ti-arm-clang clean
    • gmake -s -C examples/mmw_demo/motion_and_presence_detection/xwrL64xx-evm/m4fss0-0_freertos/ti-arm-clang all

    4. Attaching the motion_and_presence_detection appimage already made for MX25R1635F, you can use the above steps as reference in case you need any other part change. You should be able to flash the below appimage and run the motion_and_presence_detection Out-Of-Box Demo.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/motion_5F00_and_5F00_presence_5F00_detection_5F00_demo.release_2800_1_2900_.appimage

    Regards

    Ankit

  • 0
    Prodigy 220 points

    Hi Mohanty-san

    Thank you for your answer and sorry for the late reply. 
    I followed the steps you suggested and ran the qspi_flash_transfer project, but I got an error. The error message is "QSPI read data mismatch!!!" and the likely cause of the error is Flash_write or Flash_read function.

    Another problem is that ATE Calibration is required to run the motion_and_detection demo, but it does not work properly with unsupported Flash memory. Is there any way to solve this problem?

  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Hello,

    Please confirm the exact Flash memory you are using, is it MX25V1635F or the recommended MX25R1635F. Also check if the Quad Enable(QE bit) is set to 1.

    Could you kindly provide the .js file so that we can debug more

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    Prodigy 220 points

    Hello,

    I checked the QE bit, set 1 and tried it, but I got the same error. I will attach the json file (MX25R1635F.json), so please check it.

    /cfs-file/__key/communityserver-discussions-components-files/1023/MX25R1635F.txt

    And also, do you have any answers for the ATE Calibration question?

  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Thanks,

    I am checking with the concerned team. Meanwhile, can you confirm if you are using mmWave Lowpower SDK version 5.2 or 5.3.

    Regards

    Ankit

  • 0
    Prodigy 220 points

    Thank you for checking. I use SDK version 5.3.

  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Hi,

    The device ID might not have been changed in the QSPI flash transfer appimage, which could be the cause of the QSPI data mismatch issue. Both the ATE_calibration and the motion and presence detection demo should function when the updated appimage has been flashed on the device.

    Please Flash the device with the below QSPI flash transfer appimage.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/qspi_5F00_flash_5F00_transfer.release_5F00_2815.appimage

    Once done you should see all the tests passed.

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    Prodigy 220 points

    Hello,

    I flashed the attached appimage and tried to run "QSPI flash transfer", but I got the same log as before.

    Ankit Mohanty said:
    Both the ATE_calibration and the motion and presence detection demo should function when the updated appimage has been flashed on the device.

    Let me ask you a question about the above comment. How do I update appimage? Shuld I update with SysConfig?
    In particular, ATE Calibration is provided in binary and the source code is not publicly available, so I don't know how to update it.

  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Yes, you should update the device ID using the SYSCONFIG tool.

    The ATE_calibration doesn't need to be updated as it doesn't perform a device ID check to check flash compatibity, if the QSPI flash is suppoerted by mmWave sensor it shall work.

    The device ID only needs to be updated for qspi_flash_transfer & OOB demo appimages. Please do check using the SYSCONFIG tool if the device ID in (appimage/sysconfig) file matches with the ID specified in the datasheet of the QSPI Flash.

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    Prodigy 220 points

    Hi,

    Thank you for your answer. I understood that I should update using the SysConfig tool.

    Ankit Mohanty said:
    The ATE_calibration doesn't need to be updated as it doesn't perform a device ID check to check flash compatibity, if the QSPI flash is suppoerted by mmWave sensor it shall work.

    Let me ask you some question about the above comment. 

    1. Is it supported by QSPI Flash of manufacturers other than MX25V1635F and Macronix?
    2. How do I know if the QSPI Flash I want to use is supported by the mmWave sensor?
    3. If the QSPI Flash I want to use is not supported by the mmWave sensor, should I update ATE Calibration?
  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Hi,

    1. Yes, it is supported by QSPI Flash of manufacturers other than MX25V1635F and Macronix.

    2. Please check the below document for the list of QSPI Flash supported by mmWave sensors.

    Flash Variants Supported by the mmWave Sensor (Rev. D) (ti.com)

    3. If the flash variant is not supported, the QSPI flash operation shall not be possible.

    Please do confirm the QSPI flash you are using is it MX25V1635F or MX25R1635F.

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    Prodigy 220 points

    Hello,

    Thank you for your answer.

    Ankit Mohanty said:
    2. Please check the below document for the list of QSPI Flash supported by mmWave sensors.

    Regarding question no.2, attached document does not mention xWRL6432. Does this document also support xWRL6432?

    Ankit Mohanty said:

    3. If the flash variant is not supported, the QSPI flash operation shall not be possible.

    Please do confirm the QSPI flash you are using is it MX25V1635F or MX25V1635R.

    Regarding question no.3, Can I use QSPI Flash other than MX25V1635F or MX25V1635R to operate ATE Calibration with IWRL6432?

  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Hi,

    2. Yes, all the supported flash parts for xWR1642 ES2.0, xWR1842 ES1.0, xWR1443 ES3.0, and xWR6843 ES1.0 & ES2.0 devices will also support xWRL6432.

    3. If the flash variant is supported by xWRL6432 you can operate the ATE Calibration.

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    Prodigy 220 points

    Hello,

    Ankit Mohanty said:
    2. Yes, all the supported flash parts for xWR1642 ES2.0, xWR1842 ES1.0, xWR1443 ES3.0, and xWR6843 ES1.0 & ES2.0 devices will also support xWRL6432.

    Thank you for your answer. I understand your answer above.

    Ankit Mohanty said:
    Please do confirm the QSPI flash you are using is it MX25V1635F or MX25V1635R.

    Let me confirm. In the previous comment above, it said MX25V1635R, but is it a mistake to write MX25R1635F?

  • 0 in reply to ryo.sugiura
    TI__Genius 9680 points

    Hi,

    Correction: It should be MX25R1635F not MX25V1635R.

    Regards

    Ankit

  • +1 in reply to Ankit Mohanty
    Prodigy 120 points

    As Mr. Sugiura answered, unfortunately, at this time, modules with replaced flash memory do not work properly. However, this problem seems to have deep roots, so I will consider a new approach before asking the question on E2E.Thank you.