• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 176 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.

AWR2944EVM: AWR2944 OoB mmwDemo:/>cfarCfg -1 0 2 8 4 3 0 15 1 Error: Invalid usage of the CLI command Error -1

Tamas Kovago
Expert 3420 points
Part Number: AWR2944EVM
Other Parts Discussed in Thread: AWR2944, UNIFLASH,

Hi Champs,

I've been working on getting the AWR2944 EVM OoB demo up and running. While the Out_Of_Box_Demo_User_Guide.html guide I'm using provides valuable information, the frequent references to other documents make the initial experience a bit complicated. Understanding which SBL to use requires delving into Uniflash and the SDK docs. Additionally, locating the OoB demo outside the SDK in a separate toolbox adds to the complexity.

For reference, these are the steps I've made so far:

01. download / install mmwave_mcuplus_sdk_04.04.01.02
02. download / install radar_toolbox_1_30_01_03
03. download / install UniFlash
04. set the board to Flashing mode: 101 (SOP mode 5) = Flashing mode J17 closed; J18 open; J19 closed
05. plugin XDS110 usb connector
06. plugin 12V barrel connector
07. start uniflash -> autodetect shows AWR2944EVM
08. sbl Image: e:\ti\mmwave_mcuplus_sdk_04_04_01_02\mmwave_mcuplus_sdk_04_04_01_02\tools\awr294x\sbl_qspi.release.tiimage
09. app Image: e:\ti\radar_toolbox_1_30_01_03\source\ti\examples\Out_Of_Box_Demo\prebuilt_binaries\out_of_box_2944.appimage
10. power cycle
11. set COM port (COM13)
12. load image
13. set the board to Functional mode 001 (SOP mode 4) = J17 open; J18 open; J19 closed
14. power cycle
15. dev.ti.com/.../
16. platform -> AWR294x
17. send config to mmwave device
18. port COM13/115200;
19. port C0M12/custom baudrate 312500

mmwDemo:/>sensorStop Ignored: Sensor is already stopped Done
mmwDemo:/>flushCfg Done
mmwDemo:/>dfeDataOutputMode 1 Done
mmwDemo:/>channelCfg 15 15 0 Done
mmwDemo:/>adcCfg 2 0 Done
mmwDemo:/>adcbufCfg -1 1 1 1 1 Done
mmwDemo:/>lowPower 0 0 Done
mmwDemo:/>profileCfg 0 77 186 7 57.14 0 0 70 1 256 5209 0 0 30 Done
mmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1 Done
mmwDemo:/>chirpCfg 1 1 0 0 0 0 0 4 Done
mmwDemo:/>chirpCfg 2 2 0 0 0 0 0 8 Done
mmwDemo:/>chirpCfg 3 3 0 0 0 0 0 2 Done
mmwDemo:/>frameCfg 0 3 16 0 256 100 1 0 Done
mmwDemo:/>lowPower 0 0 Done
mmwDemo:/>guiMonitor -1 1 1 0 0 0 1 Done
mmwDemo:/>cfarCfg -1 0 2 8 4 3 0 15 1 Error: Invalid usage of the CLI command Error -1

1. what do I do wrong?
2. demo visualizer suggests: "(*) For the Demo Output Data Port, please select the baudrate as custom and set the value as 3125000 for both AM273X and AWR294X" but issuing queryDemoStatus command shows: Data port baud rate: 892857 Which is correct?
3. what is the rationale of having the toolbox separated from SDK?
4. Ensuring a seamless initial experience when setting up a demo or using new tools is pivotal. However, encountering difficulties due to fragmented documentation or scattered resources can be challenging. It's evident that the team has invested significant effort in creating comprehensive collateral. Yet, after browsing forums, I noticed numerous frustrated customer posts echoing the sentiment of information being too scattered. While aiming for universal documentation across multiple devices is commendable, it might be beneficial to contemplate the addition of a step-by-step, product-tailored guide, especially for the OoB project as mentioned earlier. This tailored guide would offer a clear, cohesive path for users, ensuring a smoother onboarding experience."

//---------------------------------------------LOGS ------------------------------------------------------------------------------------------------

Boot log:
mmwDemo:/>
Starting QSPI Bootloader ...
INFO: Bootloader_loadSelfCpu:207: CPU r5f0-0 is initialized to 300000000 Hz !!!
[BOOTLOADER_PROFILE] Boot Media : NOR SPI FLASH
[BOOTLOADER_PROFILE] Boot Media Clock : 80.000 MHz
[BOOTLOADER_PROFILE] Boot Image Size : 419 KB
[BOOTLOADER_PROFILE] Cores present : unknown c66ss0 r5f0-0
[BOOTLOADER PROFILE] System_init : 83us
[BOOTLOADER PROFILE] Drivers_open : 16us
[BOOTLOADER PROFILE] LoadHsmRtFw : 5us
[BOOTLOADER PROFILE] Board_driversOpen : 2706us
[BOOTLOADER PROFILE] CPU load : 435546us
[BOOTLOADER_PROFILE] SBL Total Time Taken : 438359us
Image loading done, switching to application ...
INFO: Bootloader_socCpuResetRelease:261: PBIST memory tests exeucted by RBL, RINFOL : 0xC0A0 and RINFOU : 0x0
INFO: Bootloader_runCpu:155: CPU r4 is initialized to 200000000 Hz !!!
INFO: Bootloader_runCpu:155: CPU c66ss0 is initialized to 360000000 Hz !!!
INFO: Bootloader_runSelfCpu:217: All done, reseting self ...
******************************************

AWR294X MMW Demo 04.04.01.00

******************************************

//---------------------------------------------------------------------------------------------------------------------------------------------***********************************************

mmwDemo:/>version
Platform : AWR294X
RF F/W Version : 02.04.05.03.22.04.20
RF F/W Patch : 02.04.09.02.23.06.12
mmWaveLink Version : 02.04.06.06
Die ID Val0 : 5503216
Die ID Val1 : 22
Die ID Val2 = 24, Die ID Val3 = 25
ProcChain : DDM
mmWave SDK Version : 04.04.01.00
Done

//---------------------------------------------------------------------------------------------------------------------------------------------********************************************
mmwDemo:/>queryDemoStatus
Sensor State: 0
Data port baud rate: 892857
Done

Thanks and regards

Tamas

  • 0
    TI__Mastermind 20605 points

    Hi Tamas,

    Please find the responses to your questions as follows:

    1. Can you please try to run the demo from the SDK? Also, can you tell me which .cfg file was used in your case? There are 2 different demos on the 2944, the DDM and TDM based demos. The one in the RTB is for DDM and looking from your chirp config, the modulation seems to be for TDM. Therefore, I suggest you use the right set of configs with the right demo and try the evaluation. I will however take the feedback to appropriately name the appimage in the upcoming releases.
    2. The right baud rate is 3125000. (Again, try the right demo with right config)
    3. The SDK provides a set of tools to develop software on the AWR device. The toolbox is a collection of utility tools and example projects to demonstrate the applications of the AWR devices. These two are separate but the dependency is that the RTB requires the SDK components to be built and run.
    4. Thank you for your feedback! Will take this up to the team to see what can be done going further.

    Regards,

    Kaushik

  • 0 in reply to Kaushik Gowda
    TI__Expert 3420 points

    Dear Kaushik,


    First of all thank you very much for your answer:

    1.1: I haven't found the OoB in the SDK. Could you please share the exact path where it resides?

    1.2: The OoB user's guide doesn't mention DDM/TDM as separate images. The guide is written for TDM, but there's only one prebuilt .appimage for 2944, which is DDM. Are there plans to expand the guide to include these details and provide the binary for TDM?

    1.3: Is there any pre-built cfg file that I can send to the device in DDM mode? At this stage, my goal is to visualize plots. I've learned from a different e2e thread that there isn't a graphical way to configure DDM settings, so one must compile the CFG file manually.

    2. OK - noted

    3. OK - understood

    4. OK - thank you. I highly appreciate it. I believe this will d make our customers' OoB experience much smoother.

    Thanks and regards

    Tamas

  • +1 in reply to Tamas Kovago
    TI__Mastermind 20605 points

    Hi Tamas,

    Happy new year!

    Please find my responses below:

    1. mmwave_mcuplus_sdk_04_04_01_02\mmwave_mcuplus_sdk_04_04_01_02\ti\demo\awr294x\mmw (There are various appimages with different usecases with appropriate naming here). You can also find additional info in the mmwave_sdk_userguide.pdf in the docs folder of the SDK.
    2. We will update the documents for the RTB OOB projects in future releases. This has been raised as a ticket internally for now.
    3. Yes. You can find the same in the mmwave SDK demo folder as well in the following path:
       mmwave_mcuplus_sdk_04_04_01_02\mmwave_mcuplus_sdk_04_04_01_02\ti\demo\awr294x\mmw\profiles\ddm_awr2944\
    4. One more way to configure, run and visualizer the DDM demo would be to use the mmWave Demo Visualizer that can be found in the following link.
      mmWave Demo Visualizer (ti.com)

    Hope this enables you to evaluate the demo. Kindly let me know if otherwise.

    Best regards,

    Kaushik

  • 0 in reply to Kaushik Gowda
    TI__Expert 3420 points

    Hi Kaushik,

    Thank you for all the hints and assistance. It's now functioning in TDM mode!


    I believe my main confusion came from naming conventions; in the toolbox, we refer to the project as OoB, while the OoB guide aims to be universal across multiple devices. However, the SDK contains the same under the name mmw.
    The MMWAVE MCUPLUS SDK User Guide users guide is well-written and helpful.

    Here is a recap of the step-by-step proecess that worked for me:

    01. download / install mmwave_mcuplus_sdk_04.04.01.02
    02. download / install radar_toolbox_1_30_01_03
    03. download / install UniFlash
    04. set the board to Flashing mode: 101 (SOP mode 5) = Flashing mode J17 closed; J18 open; J19 closed
    05. plugin XDS110 usb connector
    06. plugin 12V barrel connector
    07. start uniflash -> autodetect shows AWR2944EVM
    08. sbl Image: e:\ti\mmwave_mcuplus_sdk_04_04_01_02\mmwave_mcuplus_sdk_04_04_01_02\tools\awr294x\sbl_qspi.release.tiimage
    09. app Image: e:\ti\mmwave_mcuplus_sdk_04_04_01_02\mmwave_mcuplus_sdk_04_04_01_02\ti\demo\awr294x\mmw\awr2944_mmw_demoTDM.appimage
    10. power cycle
    11. set COM port (COM13)
    12. load image
    13. set the board to Functional mode 001 (SOP mode 4) = J17 open; J18 open; J19 closed
    14. power cycle
    15. dev.ti.com/.../
    16. platform -> AWR294x
    17. send config to mmwave device
    18. port COM13/115200;
    19. port C0M12/custom baudrate 3125000
     
    Thanks again.
    Tamas