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.

AWR1243: Migration from ES 2.0 Silicon to XA1243FPBGABL

Part Number: AWR1243
Other Parts Discussed in Thread: UNIFLASH

We were doing some initial development with the ES 2.0 Silicon and are migrating to the XA1243FPBGABL release. To minimize variables we would like to continue to use the DFP 1.0 libraries that we are currently using when updating the HW to the released XA1243FPBGABL silicon.

Are there any issues with this.

  • HI,

    We will be able to get back to you after Jan 1st

    thank you
    Cesar

  • Hello RJ,

    DFP 1.0 cannot be used for the ES3.0 devices directly. It would be best for you to move to DFP 1.2.5 for the ES3.0  silicon version.

    Regards,

    Vivek

  • Thanks Vivek. We'll update our Processor code to include the libraries with DFP 1.2.5.

    In our initial test going from ES 2.0 to 3.0, we're having the AWR1243's replaced on PCBs that we know are working correctly. We want to run our ATP tests on the PCBs with ES 2.0 and then with ES 3.0.

    Our PCB has the Flash device for the ES 2.0 AWR1243. Will there be any issue having this Flash device on the PCB connected to the ES 3.0 Silicon with MSS (1.10.0.23) and RSS (2.0.0.20) code that we are using with the ES 2.0 Silicon?

    Thanks.

  • Hello RJ,

    I assume you are trying to download the FW from the serial flash and not load it from the host processor over SPI. When you upgrade to 1243 ES3.0 silicon you can have the serial flash connected but update the firmware in the flash with the DFP 1.2.5 firmware.

    Regards,
    vivek

  • Thanks Vivek. That is exactly what we're trying to do.

    With the previous DFP (1.0.0) there were 3 binary files for loading, masterss.bin, memswap.bin, and radarss.bin.

    In the 1.2.5 DFP, there are only 2 binary files, masterss.bin and radarss.bin.

    Is there a concern if we leave the previous memswap.bin in the Flash?

  • Hello RJ,

    In the ES3.0 silicon you need to use a single metaimage.bin file (available in the firmware folder of the DFP package) and not three separate files.

    Regards,

    Vivek

  • Hi Vivek,

    Question on the programming of the metaimage.bin file. When we had 3 individual *.bin files we followed the examples in the UniFlash v4 User Guild for mmWave Devices. Figure 6 showed how to load in multiple images. Now that there is only one image, does the metaimage go in the RadarSS Slot, the MSS Slot, or the Image 3 or Image 4 Slot?

    Regards,

    RJ

  • Hello RJ,

    In Uniflash you can see that the first section is "metaimage 1/ Radar SS". The single meta image needs to be loaded into the Radar SS slot.

    Regards,

    Vivek