• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 1296 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.

AWR1243BOOST: cannot use the second board

Ilia K.
Prodigy 250 points
Part Number: AWR1243BOOST
Other Parts Discussed in Thread: AWR1243

Hi,

I have two identical bundles of awr1243-boost+mmwave-devpack+tsw1400evm. I want to run a simple test using mmwavelink_example supplied in DFP (tried both v7 and v9).

For each one of the two bundles I can connect it alone to the PC and successfully run mmwavelink_example.

I can connect both bundles and successfully run mmwavelink_example as is. This way it only talks to the first awr1243-boost board and ignores the second.

I want mmwavelink_example to talk to (A) the second board, and then (B) to both. I modify MMWL_App() function in mmw_example.c file and change a single line:

unsigned char deviceMap = RL_DEVICE_MAP_CASCADED_1;

To implement (A) I change the line into:

unsigned char deviceMap = RL_DEVICE_MAP_CASCADED_2;

To implement (B) I change the line into:

unsigned char deviceMap = RL_DEVICE_MAP_CASCADED_1 | RL_DEVICE_MAP_CASCADED_2;

When I run the resulting binary it cannot connect to the second board.

Example output for (A):

=========== mmWaveLink Example Application ===========
rlComIfOpen Callback Called for Device Index [1]
Got 16 devices connected
Device 0: TSW1400 A , SN: KS952873A
Device 1: AR-DevPack-EVM-012 D , SN: FT1DTDF6D
Device 2: TSW1400 B , SN: KS952873B
Device 3: TSW1400 C , SN: KS952873C
Device 4: TSW1400 D , SN: KS952873D
Device 5: AR-DevPack-EVM-012 A , SN: FT1DQOR8A
Device 6: AR-DevPack-EVM-012 B , SN: FT1DQOR8B
Device 7: AR-DevPack-EVM-012 A , SN: FT1DTDF6A
Device 8: AR-DevPack-EVM-012 C , SN: FT1DQOR8C
Device 9: AR-DevPack-EVM-012 D , SN: FT1DQOR8D
Device 10: TSW1400 A , SN: KS1023607A
Device 11: TSW1400 B , SN: KS1023607B
Device 12: TSW1400 C , SN: KS1023607C
Device 13: AR-DevPack-EVM-012 B , SN: FT1DTDF6B
Device 14: TSW1400 D , SN: KS1023607D
Device 15: AR-DevPack-EVM-012 C , SN: FT1DTDF6C
Error: mmWave Device is not Connected
rlDeviceEnable Callback is called by mmWaveLink for Device Index [1]
mmWave Device Power on failed for deviceMap 2 with error -8

=========== mmWaveLink Example Application execution Failed ===========

Example output for (B):

=========== mmWaveLink Example Application ===========
rlComIfOpen Callback Called for Device Index [0]
Got 16 devices connected
Device 0: TSW1400 A , SN: KS952873A
Device 1: AR-DevPack-EVM-012 D , SN: FT1DTDF6D
Device 2: TSW1400 B , SN: KS952873B
Device 3: TSW1400 C , SN: KS952873C
Device 4: TSW1400 D , SN: KS952873D
Device 5: AR-DevPack-EVM-012 A , SN: FT1DQOR8A
Device 6: AR-DevPack-EVM-012 B , SN: FT1DQOR8B
Device 7: AR-DevPack-EVM-012 A , SN: FT1DTDF6A
Device 8: AR-DevPack-EVM-012 C , SN: FT1DQOR8C
Device 9: AR-DevPack-EVM-012 D , SN: FT1DQOR8D
Device 10: TSW1400 A , SN: KS1023607A
Device 11: TSW1400 B , SN: KS1023607B
Device 12: TSW1400 C , SN: KS1023607C
Device 13: AR-DevPack-EVM-012 B , SN: FT1DTDF6B
Device 14: TSW1400 D , SN: KS1023607D
Device 15: AR-DevPack-EVM-012 C , SN: FT1DTDF6C
SPI port opened (PortNum=7)
IRQ & I2C port opened (PortNum=13)
Board Control port opened (PortNum=15)
Generic GPIO port opened (PortNum=9)
rlComIfOpen Callback Called for Device Index [1]
Got 16 devices connected
Device 0: TSW1400 A , SN: KS952873A
Device 1: AR-DevPack-EVM-012 D , SN: FT1DTDF6D
Device 2: TSW1400 B , SN: KS952873B
Device 3: TSW1400 C , SN: KS952873C
Device 4: TSW1400 D , SN: KS952873D
Device 5: AR-DevPack-EVM-012 A , SN: FT1DQOR8A
Device 6: AR-DevPack-EVM-012 B , SN: FT1DQOR8B
Device 7: AR-DevPack-EVM-012 A , SN: FT1DTDF6A
Device 8: AR-DevPack-EVM-012 C , SN: FT1DQOR8C
Device 9: AR-DevPack-EVM-012 D , SN: FT1DQOR8D
Device 10: TSW1400 A , SN: KS1023607A
Device 11: TSW1400 B , SN: KS1023607B
Device 12: TSW1400 C , SN: KS1023607C
Device 13: AR-DevPack-EVM-012 B , SN: FT1DTDF6B
Device 14: TSW1400 D , SN: KS1023607D
Device 15: AR-DevPack-EVM-012 C , SN: FT1DTDF6C
Error: mmWave Device is not Connected
rlDeviceEnable Callback is called by mmWaveLink for Device Index [0]
rlDeviceEnable Callback is called by mmWaveLink for Device Index [1]
mmWave Device Power on failed for deviceMap 3 with error -8

=========== mmWaveLink Example Application execution Failed ===========

It looks like a bug in mmwlstudio.lib. Can you please check this case and help me with finding a solution? If I'm not correct, please guide me to the changes I need to implement. I must be able to talk to two boards simultaneously (like in case (B) above).

Thanks.

  • 0
    TI__Guru 69960 points

    Hello Spring,

    DFP mmwlstudio.lib supports only one AWR1243 connection, so connecting with two boards at a time will not work.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 250 points
    Is there a way to connect to two awr1243 from PC without implementing the equivalent of mmwlstudio.lib from scratch?
  • 0 in reply to Ilia K.
    TI__Guru 69960 points
    Communication mode for AWR1243 is SPI which is emulated using FT4232HL chip of mmWave-DEVPACK to connect with PC. And same FTDI provides reset and SOP control of device over USB.

    So, it's not possible to connect to AWR1243 from PC without implementing a wrapper on top of FTDI dll to control device over FT4232HL chip of mmwave-DEVPACK. mmwlstudio.lib provides a wrapper on top of FTDI dll to control FT4232FL and further control AWR1243 device over USB.



    Regards,
    Jitendra