• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 818 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:

AWR1243: Firmware uploading error to XIWR1243P

AWR1243: Error while running mmwave example with AWR1243P device and DCA1000EVM data capture Card

Nishant G
Expert 1600 points
Part Number: AWR1243
Other Parts Discussed in Thread: MMWAVE-DFP, DCA1000EVM,

Hello,

With reference to my previous post, I downloaded the new firmware(xwr12xx_metaImage.bin  from mmWave-DFP 1.2) for AWR12433P. I wanted to test if the new chip is able to send data correctly. For this purpose, I ran mmwave example from mmWave-DFP 1.2 using DCA1000EVM board. However, I am getting an error "mmwave device power on failure". Is the new firmware compatible with DCA1000 EVM? 

I have another board with similar hardware design which uses AWR1243 instead of 1243P, and if I use the original firmware that you use to run all 1243 devices, I am not getting any error and the application is executing successfully. Does that mean that the the new firmware in the  cascaded board with AWR1243P is causing any problem? Or is there any particular hardware aspect to be taken into consideration for AWR1243P?

PS: An interesting observation that I found- If i connect the AWR1243P Cascaded board with DCA1000 and I power on the DCA1000, I see few red LED lights(DATA_TRAN_PRG, SD_DETECT, SD_FULL, SPARE etc) on the board that lits up (for initialization I guess). If I run the application before the red LED lights turn off, the mmwave example application runs successfully. However, after the LED turns off, it gives the same Power On failure error.

Other few hardware connection details for reference: MOSI pin, SPICLK and SPI_HOST_INTR is pulled down to ground using 100K pull down resistor.

Please let me know if you know the solution to this problem. 

Thank you!

Best Regards,

Nishant

  • 0
    TI__Guru 69960 points
    Hi Nishant,
    Is this custom board (1243P) or EVM?
    Is it possible if you can try same experiment on AWR1243P with DevPack? This way we'll take DCA1000 out of picture.
    If you have custom board with AWR1243P then I would request you to check this board schematic, as you are saying it's working with AWR1243 and AWR1243P board is working with DCA100 but under some condition.

    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    TI__Guru 58035 points
    Hello Nishant,
    The DCA1000 is capable of connecting to only a single AWR1243/AWR1243P device. Could you clarify how are you using it in a cascade configuration? As indicated by Jiten in the previous post, providing more details about your setup will help us understand the problem better.

    Regards,
    Vivek
  • 0 in reply to Vivek Dham
    Expert 1600 points

    Hello Vivek and Jitendra,

    In  my current setup, there are three AWR1243P (1 Master and 2 slaves) connected in cascade configuration. The hardware is very similar to Fig 1 and Fig 2 of the AWR1243 Cascade Report (Rev A) (http://www.ti.com/lit/an/swra574a/swra574a.pdf) except that there are three 1243P Chips instead of 2. The Osc_CLKOut from the master is given to a CLK DRIVER which drives the two clocks. Each has its own flash chip. Sync_Out from Master is given to a Sync_driver that is connected to Sync_in of the two Slave devices.

    For testing the data collection of the cascaded system, I am connecting DCA1000 individually to each 1243P device, which means one DCA1000 to Master and on each for each slave. The hardware board layout of cascaded AWR1243 and cascaded 1243P is exactly same. We have assumed that the pin configurations of AWR1243 and AWR1243P are same too. Could you confirm this as I couldn't find any datasheet for 1243P?

    Regarding firmware, I looked at the mmwave_dfp 1.2 release notes and it doesn't mention AWR1243P in it for xwr12xx_metaImage.bin file. It just mentions support for ES3.0 AWR1243. Are they referring to AWR1243P in this document? Unfortunately, I cannot connect a devpack with my cascaded AWR1243P board. I cannot test it as I do not have a AWR1243P EVM board or a board that is similar to it. Were you able to collect data from AWR1243P with DCA1000 using the same firmware at your end?

    I hope I was able to clarify my hardware setup. I look forward to your reply. 

    Thank you!

    Regards,

    Nishant

  • 0 in reply to Nishant G
    Expert 1600 points
    Hello Vivek and Jitendra,

    I think we have resolved the issue. The problem was in the hardware board layout, which I hadn't noticed before. The firmware is good. Thanks for your time and help!

    Best Regards,
    Nishant
  • 0 in reply to Nishant G
    TI__Guru 58035 points
    Hello Nishant,
    Thanks for the confirmation !

    Regards,
    Vivek