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: Application Inquiy

Part Number: IWR6843AOP
Other Parts Discussed in Thread: UNIFLASH, , IWR6843, MMWAVEICBOOST

Hello Team,

Posting on behalf of my customer:

I am trying to program an IWR6843AOP on a custom board using the SPIA interface connected to an FT2232 chipset. I am using the Uniflash Tool to flash the out of the box demo and it detects the XDS100v2 USB Debug
Probe (which is actually not connected) and two COM Ports provided by the FTDI chip. 

When trying to flash the out of the box demo, I get an error message:
error: Initial response from the device was not received. Please power cycle device before re-flashing.
error: Not able to connect to serial port. Recheck COM port selected and/or permissions.

I would like to clarify following points:

1. Is it necessary to flash an image over QSPI using a FT4222H or does the SPIA interface in combination with the FT2232 work as well? According to the App Note "IWR6843 Bootloader Flow" for a similar chipset, this should be possible (section 2.2).

2. Is an external Flash memory (e.g. MX25R1635FZUIH0) necessary in both cases (SPI and QSPI)?

3.Is it necessary to set the SOP pins first in flashing mode and then in functional mode to flash an image over SPIA? According to the document "IWR6843 Bootloader Flow" (Figure 4), this should be possible in functional mode as well.

Regards,

Renan

  • Hello Renan,

    Can you please pass this message onto your customer:

    Can you please send an image of the switch configuration being used on the AOP and the MMWAVEICBOOST? 

    I am unsure whether you simply want to flash the device with SPI, or if you want to implement a secondary bootloader, in which you can send an image to the device over SPI in functional mode. It sounds to me like you want the latter.

    If that is the case, please refer to the secondary bootloader documentation present in the SDK here:
    <SDK3_INSTALL_DIRECTORY>/packages/ti/utils/sbl/docs/SBL_design.pdf

    Section 4.10 will instruct you on how to perform this operation. Note, this application reads in the image over UART, then rewrites the SFLASH with the image via QSPI. 

    I may have been incorrect in the assumption I made about what you intend to do, though. If so, can you please clarify what your goal is?

    Regards,
    Luke

  • Hello Luke,

    Please see response from my customer:

    <My overall goal is to set the RF parameters and enable raw data
    streaming to be output on the LVDS interface. As a first step towards
    this, I would like to flash the AOP's ROM via SPI. If possible, I would
    like to avoid using an external Flash memory. Therefore I do not need
    the secondary bootloader, right?
     
    I am not using the MMWAVEICBOOST board. Instead, I placed the AOP on a
    custom board. I can manually set the SOP pins.

    Regards,

    Renan

  • Hello,

    Please give us more time to get back to you with answers

    Best Regards,

    Pedrhom Nafisi

  • Hello Renan,

    I understand. Thank you for providing more context. To answer your questions...

    Yes, you can utilize the SPI bootmode with the native bootloader without needing to develop a secondary bootloader, like is said in IWR6843 Bootloader Flow. Specifically, look at the Basic Bootloader Flow flowchart on page 5 of the document and the Bootmode - SPI section on page 7.

    No, you do not need to use an external flash and the QSPI interface. You can provide the image to the device via the SPI-interface alone, but you will need to provide the image from some sort of host device.

    No, if providing the image in the SPI Bootmode, the device should remain in functional mode. It does not need to be in the flashing SOP-mode. 

    Also, if you are not aware, we provide the DCA1000 board that quickly enables ADC data capture.

    Regards,
    Luke