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.

IWR6843AOP: Reserving space in External flash ( MX25R1635FZUIH0-TR)

Part Number: IWR6843AOP

Tool/software:

I’m working on a project using the IWR6843AOP and based it on the example from TI’s radar toolbox:

C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\Overhead_3D_People_Tracking.

In my design, I’m using the MX25R1635FZUIH0-TR external flash chip, and I want to:

  1. Understand how flash memory is mapped in this project — especially how much space is already reserved for the radar application (MSS, BSS, etc.).

  2. How to check where and how the program image is stored in flash in the sample project.

  3. I also want to store custom settings and log data into flash. For that, I need to reserve a dedicated region in flash for user data, and make sure it does not overlap with the application code/data.

So I need help identifying the flash layout in this project and how to modify it safely for user-defined storage.

  • Hello.

    Understand how flash memory is mapped in this project — especially how much space is already reserved for the radar application (MSS, BSS, etc.).

    Flash memory is not mapped to the project like it is for RAM.  The on-chip memory is separated into MSS, BSS, DSS, etc., and the details can be found in the linker file for the project.  The flash chip memory can be organized however you see fit and based on your specific flash chip.  For the chip on the EVM, it is partitioned into four sections that can store any information you choose, most commonly the application(s).

    How to check where and how the program image is stored in flash in the sample project.

    You can refer to the flash/qspi driver for how to read what is in flash.  However, the application that you load into SFLASH will not load if not loaded correctly so you can determine if it was flashed correctly based on the behavior of the device at power on.

    I also want to store custom settings and log data into flash. For that, I need to reserve a dedicated region in flash for user data, and make sure it does not overlap with the application code/data.

    This will again be based on how you set up your flash chip.  If you wish to reserve a section, just make sure that you outline this address in your application software, and also make sure that your flashing tool allows you to customize where you load the application into SFLASH or make sure that whatever predetermined location doesn't overlap with your reserved section.

    Sincerely,

    Santosh