• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 1207 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:

MMWAVE-STUDIO: mmWave Configuration File Json file error

MMWAVE-STUDIO: MMWAVE-STUDIO: mmWave Configuration File Json file error！！！

user6446804
Prodigy 240 points
Part Number: MMWAVE-STUDIO
Other Parts Discussed in Thread: AWR1642

I generated the JOSN configuration file of millimeter wave radar through mmWaveSensingEstimato. I hope to load this configuration file directly through mmWave Configuration File in import_export in mmwave_studio, so that I don't need to carry out complicated configuration process.However, during the configuration process, some problems appeared.This is my OUTPUT window.

22:04:05] [RadarAPI]: Single Chip Configuration
[22:04:05] Capture Setup JSON Configuration is imported and loaded. DONE.
[22:04:11] [RadarAPI]: Single Chip Configuration
[22:04:11] Capture Setup JSON Configuration is imported and loaded. DONE.
[22:04:14] [RadarAPI]: ar1.CaptureCardConfig_EthInit("192.168.33.30", "192.168.33.180", "12:34:56:78:90:12", 4096, 4098)
[22:04:14] [RadarAPI]: ar1.CaptureCardConfig_Mode(1, 2, 1, 2, 3, 30)
[22:04:14] [RadarAPI]: ar1.CaptureCardConfig_PacketDelay(25)
[22:04:14] [RadarAPI]: Sending fpga command to DCA1000
[22:04:14] [RadarAPI]: 
[22:04:14] FPGA Configuration command : Success
[22:04:14] [RadarAPI]: Sending record command to DCA1000
[22:04:15] [RadarAPI]: 
[22:04:15] Configure Record command : Success
[22:04:15] [RadarAPI]: ar1.GetCaptureCardFPGAVersion()
[22:04:15] [RadarAPI]: Sending fpga_version command to DCA1000
[22:04:16] [RadarAPI]: 
[22:04:16] 
[22:04:16] FPGA Version : 2.8 [Record]
[22:04:16] 
[22:04:17] [RadarAPI]: Single Chip Configuration
[22:04:17] Capture Setup JSON Configuration is imported and loaded. DONE.
[22:04:24] [RadarAPI]: Single Chip Configuration
[22:04:24] [RadarAPI]: No of devices connected and the no of devices in the json config are matching
[22:04:33] [RadarAPI]: ar1.PowerOff()
[22:04:33] [RadarAPI]: Status: Passed
[22:04:33] [RadarAPI]: Opening Gpio Control Port()
[22:04:33] [RadarAPI]: Status: Passed
[22:04:34] [RadarAPI]: ar1.Disconnect()
[22:04:34] [RadarAPI]: ar1.Calling_ATE_DisconnectTarget()
[22:04:34] [RadarAPI]: ar1.Calling_IsConnected()
[22:04:34] [RadarAPI]: ar1.SaveSettings('C:\Users\Administrator\AppData\Roaming\RSTD\ar1gui.ini')
[22:04:34] [RadarAPI]: Opening Board Control Port()
[22:04:34] [RadarAPI]: Status: Passed
[22:04:35] [RadarAPI]: ar1.FullReset()
[22:04:35] [RadarAPI]: Status: Passed
[22:04:35] [RadarAPI]: Closing Board Control Port()
[22:04:35] [RadarAPI]: Status: Passed
[22:04:36] [RadarAPI]: Closing Gpio Control Port()
[22:04:36] [RadarAPI]: Status: Passed
[22:04:36] [RadarAPI]: ar1.SOPControl(2)
[22:04:36] [RadarAPI]: Status: Passed
[22:04:39] [RadarAPI]: ar1.Connect(6,921600,1000)
[22:04:42] [RadarAPI]: Warning: Connected with baudrate 115200
[22:04:43] [RadarAPI]: Warning: Disconnected existing BaudRate
[22:04:43] [RadarAPI]: Warning: Trying to connect with baudrate 921600
[22:04:45] [RadarAPI]: ar1.Calling_IsConnected()
[22:04:46] [RadarAPI]: ar1.SelectChipVersion("AR1642")
[22:04:46] [RadarAPI]: Status: Passed
[22:04:46] [RadarAPI]: ar1.SelectChipVersion("XWR1642")
[22:04:46] [RadarAPI]: Status: Passed
[22:04:46] Device Status : XWR1642/ASIL-B/SOP:2/ES:2
[22:04:46] [RadarAPI]: ar1.SaveSettings('C:\Users\Administrator\AppData\Roaming\RSTD\ar1gui.ini')
[22:04:51] [RadarAPI]: ar1.DownloadBSSFw("C:\\ti\\mmwave_studio_02_01_01_00\\rf_eval_firmware\\radarss\\xwr16xx_radarss.bin")
[22:04:52] [RadarAPI]: Downloading BSS Patch RPRC Binary..
[22:04:53] [RadarAPI]: ar1.GetBSSFwVersion()
[22:04:53] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[22:04:54] [RadarAPI]: ar1.GetBSSPatchFwVersion()
[22:04:54] [RadarAPI]: BSSPatchFwVersion:(01.02.05.02 (30/04/19))
[22:04:54] [RadarAPI]: ar1.DownloadMSSFw("C:\\ti\\mmwave_studio_02_01_01_00\\rf_eval_firmware\\masterss\\xwr16xx_masterss.bin")
[22:04:55] [RadarAPI]: Downloading MSS RPRC Binary..
[22:04:57] [RadarAPI]: ar1.GetMSSFwVersion()
[22:04:57] [RadarAPI]: MSSFwVersion:(01.02.05.02 (16/07/19))
[22:04:58] [RadarAPI]: ar1.PowerOn(0, 1000, 0, 0)
[22:04:58] MSS power up done async event received!
[22:04:58] [RadarAPI]: Status: Passed
[22:05:03] [RadarAPI]: ar1.SelectChipVersion("AR1642")
[22:05:03] [RadarAPI]: Status: Passed
[22:05:03] [RadarAPI]: ar1.SelectChipVersion("XWR1642")
[22:05:03] [RadarAPI]: Status: Passed
[22:05:03] Device Status : XWR1642/ASIL-B/SOP:2/ES:2
[22:05:03] [RadarAPI]: ar1.RfEnable()
[22:05:03] [RadarAPI]: Status: Passed
[22:05:03] BSS power up done async event received!
[22:05:04] [RadarAPI]: ar1.GetMSSFwVersion()
[22:05:04] [RadarAPI]: MSSFwVersion:(01.02.05.02 (16/07/19))
[22:05:04] [RadarAPI]: ar1.GetBSSFwVersion()
[22:05:04] [RadarAPI]: BSSFwVersion:(02.00.00.01 (05/10/17))
[22:05:05] [RadarAPI]: ar1.GetBSSPatchFwVersion()
[22:05:05] [RadarAPI]: BSSPatchFwVersion:(01.02.05.02 (30/04/19))
[22:05:10] [RadarAPI]: ar1.CaptureCard_DisConnect()
[22:05:10] [RadarAPI]: Status:Passed
[22:05:10] Capture Setup is Configured. DONE.
[22:05:17] [RadarAPI]: Single Chip Configuration
[22:05:17] [RadarAPI]: No of devices connected and the no of devices in the json config are matching

why thereis“No of devices connected and the no of devices in the json config are matching”

Is my configuration step wrong? If it is wrong, can you tell me in detail the process of directly configuring radar using JSON file?

What comes with the system （C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\JSONSampleFiles）also shows “No of devices connected and the no of devices in the json config are matching”.

The version of mmwave studio I use is mmWave Studio 02.01.01.00.

Can you help me demonstrate the following detailed operation process

  • 0
    TI__Mastermind 31680 points

    Hello User,

    This is not an error.

    It just means that "number of devices connected and the number of devices in the json config are matching".

    I have still summarized the steps for you, please follow the figure.

    • Choose the appropriate json setup file in step 1 and then import and setup as highlighted in steps 2 and 3.
    • After performing the above steps, you will get a message saying "Capture Setup is Configured. DONE."
    • After this, load the corresponding mmWave.json config file highlighted in step 4 and press "Import" (Step 5)
    • Press "Load" (step 6) and then "Configure Device"
    • After you've completed all the above steps, a dialog box will appear stating the "Next operation Steps". Follow those and you will be able to sucessfully capture raw ADC data using the AWR device and DCA1000.

    Hope the information provided above was clear. You could also read about the setup and config Json files in detail in the mmWave_studio_user_guide.pdf (Chapter 20 Import/export Tab operations).

    Regards,

    Ishita

  • 0 in reply to Ishita Kochar
    Prodigy 240 points

    Thank you for your reply!

    But I still don't understand what no in the “No of devices connected and the no of devices in the json config are matching” stands for,What caused this problem and how should I solve it? Whether the configuration file and hardware can't match or my hardware he didn't recognize at all. Can you give me an idea?

  • 0 in reply to user6446804
    TI__Mastermind 31680 points

    Hello User,

    As I said, this is not an error but just a message. "No." stands for "Number" here. Please proceed with the steps as mentioned and you will be able to capture data.

    Regards,

    Ishita

  • 0 in reply to Ishita Kochar
    Prodigy 240 points

    I did what you said, and the result after IMPORT was that it was impossible to configure radar at all? NO stands for numbers? Shouldn't no mean nothing? How should I solve this problem?


    [16:03:01]  [RadarAPI]: Single Chip Configuration
    [16:03:01]  [RadarAPI]: No of devices connected and the no of devices in the json config are matching
    [16:03:05]  Missing Low Power Mode Configuration for Device 0. Skipping..
    [16:03:05]  Missing LDO Bypass Configuration for Device 0. Skipping..
    [16:03:05]  Missing Per Chip Phase shifter Configuration for Device 0. Skipping..
    [16:03:05]  Missing TX Frequency and Power Limit Monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing RF Device Configuration for Device 0. Skipping..
    [16:03:05]  Missing Test Pattern Configuration for Device 0. Skipping..
    [16:03:05]  Missing Dynamic Power Save Configuration for Device 0. Skipping..
    [16:03:05]  Missing Inter Rx Gain Phase Configuration for Device 0. Skipping..
    [16:03:05]  Missing Calibration Monitoring Time Unit Configuration for Device 0. Skipping..
    [16:03:05]  Missing RF Init Calibration Configuration for Device 0. Skipping..
    [16:03:05]  Missing Run Time Calibration Configuration for Device 0. Skipping..
    [16:03:05]  Missing Advanced Frame Configuration for Device 0. Skipping..
    [16:03:05]  Missing Loopback Burst Configuration for Device 0. Skipping..
    [16:03:05]  Missing Advanced Chirp Configuration for Device 0. Skipping..
    [16:03:05]  Missing Continous Mode Configuration for Device 0. Skipping..
    [16:03:05]  Missing BPM Chirps Configuration for Device 0. Skipping..
    [16:03:05]  Missing Phase Shift Configuration for Device 0. Skipping..
    [16:03:05]  Missing Test Source Configuration for Device 0. Skipping..
    [16:03:05]  Missing Inter Chirp Block Control Configuration for Device 0. Skipping..
    [16:03:05]  Missing GP ADC Configuration for Device 0. Skipping..
    [16:03:05]  Missing PA Loopback Configuration for Device 0. Skipping..
    [16:03:05]  Missing PS Loopback Configuration for Device 0. Skipping..
    [16:03:05]  Missing IF Loopback Configuration for Device 0. Skipping..
    [16:03:05]  Missing Program Filter Configuration for Device 0. Skipping..
    [16:03:05]  Missing Program Filter Coefficients Configuration for Device 0. Skipping..
    [16:03:05]  Missing Digital Monitoring Enables Configuration for Device 0. Skipping..
    [16:03:05]  Missing Digital Monitoring Periodic Configuration for Device 0. Skipping..
    [16:03:05]  Missing Latent Fault Configuration for Device 0. Skipping..
    [16:03:05]  Missing Periodic Test Configuration for Device 0. Skipping..
    [16:03:05]  Missing External Analog Signals Monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Tx Internal Analog Signals Monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Rx Internal Analog Signals Monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Internal signals for PM, CLK and LO monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Internal signals for GPADC monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Internal signals for PLL control voltage monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Internal signals for DCC based clock monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing RX gain and phase monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing RX noise monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing RX IF stage monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing RX saturation monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Signal and image band energy monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing RX mixer input power monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Temperature sensor monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Synthesizer frequency monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Analog monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing TX power monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing TX ballbreak monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing TX BPM monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing TX gain and phase mismatch monitoring Configuration for Device 0. Skipping..
    [16:03:05]  Missing Analog fault injection Configuration for Device 0. Skipping..
    [16:03:05]  Missing Dynamic Chirps Configuration for Device 0. Skipping..
    [16:03:05]  [RadarAPI]: mmWave Device 0 Configuration is loaded. DONE.
    [16:03:16]  Low power mode configuration is mandatory for device 0.

    Thank you

  • 0 in reply to Ishita Kochar
    Prodigy 240 points

    And why there ie a "missing"?

    Thank you

  • 0 in reply to user6446804
    TI__Mastermind 31680 points

    Hello User,

    Are you using the default JSON file that comes as an example with the mmWave studio package? It seems not although.

    Because you're using AWR1642, you need to configure the device in Low power mode only. (The default script for AWR16xx takes care of this)

    The "Missing" notification is just a message informing you of all the APIs you've not configured (like some monitors etc). From what I can see, apart from the upper 1-2 APIs you've missed (like low power config), you don't need the rest of them so you can ignore them all.

    I would recommend you to first try the default script that comes with the studio package for AWR16XX, that takes care of the correct device configuration in low power mode.

    (Please be noted that "No." means "Number", and the "missing" messages are not an error")

    Regards,

    Ishita