• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 1400 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.

AWR1642: AWR1642: XDS110 hangs when both two transmitting antennas enabled for one chirp

user1756959
Prodigy 90 points
Part Number: AWR1642

Hi there,

I am using the xwr16xx mmw demo in the MMWAVE SDK 01_01_00_02. When I am setting that  both the two transmitting antennas transmit simultaneously in one chirp (chirpCfg 0 1 0 0 0 0 0 3), the console in CCS show that the sensor start successfuly first, but then the XDS110 hanged. I have tested that both 'chirpCfg 0 1 0 0 0 0 0 1' and 'chirpCfg 0 1 0 0 0 0 0 2' work perfectly. PS: channel configuration has been set to 'channelCfg 15 3 0' .

the following console output is given

CS_DAP_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 7.0.48.0)

Cortex_R4_0: Error：  (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 7.0.48.0) 

CS_DAP_0: Unable to determine target status after 20 attempts

CS_DAP_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

Cortex_R4_0: Unable to determine target status after 20 attempts

Cortex_R4_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

The dox has shown that maximum of only 2 TX can be turned in a chirp.

Following are my configuration,

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 15 3 0

adcCfg 2 1

adcbufCfg -1 0 0 1 0

profileCfg 0 77 7 7 58 0 0 68 1 256 5500 0 0 30

chirpCfg 0 1 0 0 0 0 0 3

frameCfg 0 1 32 0 100 1 0

lowPower 0 0

guiMonitor -1 1 1 1 0 0 1

cfarCfg -1 0 2 8 4 4 0 5120

cfarCfg -1 1 0 8 4 4 0 5120

peakGrouping -1 1 0 0 1 224

multiObjBeamForming -1 1 0.5

calibDcRangeSig -1 0 -5 8 256

extendedMaxVelocity -1 0

clutterRemoval -1 0

compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0

measureRangeBiasAndRxChanPhase 0 1.5 0.2

sensorStart

I am using the profile_2d.cfg provided in the xwr16xx mmw demo and I replaced the oringinal chirp configuration with 'chirpCfg 0 1 0 0 0 0 0 3', and the channel configuration has been set to 'channelCfg 15 3 0'.

Any idea?

Thanks,

Beren

  • 0
    TI__Guru 69960 points
    Hi Beren,
    Have you done any changes in mmw demo?
    As I don't see any issue in CCS XDS110 connection using default mmw demo of SDK 1.1 with your configuration and I can see plots in Visualizer.


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Prodigy 90 points

    Hi, Jitendra,

    Thanks for your help.

    I didn't change any thing in the mmw demo.

    I checked my chirp configuration again, and I found that I also changed the frameCfg with 'frameCfg 0 1 64 0 100 1 0'.  So my real configuration is

    sensorStop

    flushCfg

    dfeDataOutputMode 1

    channelCfg 15 3 0

    adcCfg 2 1

    adcbufCfg -1 0 0 1 0

    profileCfg 0 77 7 7 58 0 0 68 1 256 5500 0 0 30

    chirpCfg 0 1 0 0 0 0 0 3

    frameCfg 0 1 64 0 100 1 0

    lowPower 0 0

    guiMonitor -1 1 1 1 0 0 1

    cfarCfg -1 0 2 8 4 4 0 5120

    cfarCfg -1 1 0 8 4 4 0 5120

    peakGrouping -1 1 0 0 1 224

    multiObjBeamForming -1 1 0.5

    calibDcRangeSig -1 0 -5 8 256

    extendedMaxVelocity -1 0

    clutterRemoval -1 0

    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0

    measureRangeBiasAndRxChanPhase 0 1.5 0.2

    sensorStart

    I have tested that the XDS 110 hanged when the frameCfg was with ‘frameCfg 0 1 64 0 100 1 0’. How ever it  worked perfect when  the frameCfg was with ‘frameCfg 0 1 32 0 100 1 0’, which is same as your result.

    So could you test again with ‘frameCfg 0 1 64 0 100 1 0’?

    Thanks,

    Beren

  • 0 in reply to user1756959
    TI__Guru 69960 points
    Hello Beran,
    Even with this configuration ( ‘frameCfg 0 1 64 0 100 1 0’) also I don't see any error with CCS connection at my setup.
    Can you check power supply (5V, 3.0A), as you are using 2Tx at a time?


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Prodigy 90 points

    Hi, Jitendra,

    I checked my power supply, it was 5v with 1A. After replacing by another one with 2.4A, the XDS110 issue was gone. So the connection issue was due to that the current of the power source was not enough to support using 2Tx and the debug with CCS as the same time.

    Thanks for your help. Have a good weekend. 

    Regards,

    Beren