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.

IWRL6432BOOST: Issue with SysConfig "Load CLI Config From JSON"

Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: SYSCONFIG, IWRL6432

Hi,

First off, here's my setup

  • Windows 11
  • MMWAVE_L_SDK_05_04_00_01
  • radar_toolbox_2_00_00_06
  • I've tried with
    • CCS12.4.0.00007
    • CCS12.5.0.00007
    • CCS12.6.0.00008
  • I've tried with
    • SysConfig 1.18.0
    • SysConfig 1.19.0

I'm using the following CCS project from the radar toolbox and using CCS12.5

C:\ti\radar_toolbox_2_00_00_06\source\ti\examples\Level_Sensing\high_accuracy_low_power_sensors

I made a copy of the json file from C:\ti\MMWAVE_L_SDK_05_04_00_01\examples\mmw_demo\motion_and_presence_detection\profiles\xwrL64xx-evm\FeatureLiteBuild.json into my local project folder

I then launch the SysConfig tool from CCS, enable the Feature Lite Build, then I use "LOAD CLI Config from JSON" and select the json file.

Although there was no feedback it did anything, it didn't get stuck like it does with CCS 12.4 and CCS 12.6 so I assume it worked.

I then save everything and do a project build. It builds okay. I can open the ti_cli_mpd_demo_config.h file that SysConfig generated and see all #define settings in there.

The problem is this: if I modify the json file, load it again from SysConfig, and rebuild the project, not a single thing changes in the generated ti_cli_mpd_demo_config.h file.

This would seem to indicate the "Load CLI Config From JSON" didn't actually work. Now I'm stuck again!

How can I debug this? Is there a debug console or log I can look at to see if SysConfig did indeed load my json file?

Can somebody try this and if works, send me all your tool versions you used?

  • Hi,

    Thanks for your query. Please allow us a couple of days to respond

    Regards

  • Hello,

    Does this happen regardless of whether you use the deafult .json in the original location, as well as regardless of CCS version or Syscfg version? You can confirm via editing the syscfg in text editor view.

    Best Regards,

    Pedrhom

  • So I tried a lot of experiments using combinations of CCS and SysConfig versions. Below is a screenshot of the tools I have installed.

    I've pretty much tried all combinations of CCS versions and SysConfig versions. 

    I have two issues

    1) SysConfig hangs when opening a JSON file.

    This one is not a big issue for me at the moment but worth reporting. If I attempt to "LOAD FROM JSON" in any version of SysConfig other than 1.18.x , SysConfig hangs forever with a popup box saying 'Running external process...' . It never completes. This occurs with all versions of SysConfig except 1.18.x. This is also independent of CCS version, same results with CCS 12.4, CCS 12.5, and CCS 12.6 so it seems to be a SysConfig issue.

    - SysConfig 1.17.0    Hangs

    - SysConfig 1.18.0    Doesn't Hang

    - SysConfig 1.18.1    Doesn't Hang

    - SysConfig 1.19.0    Hangs

    - SysConfig 1.20.0    Hangs

    2) Loading a json file from SysConfig has no effect.

    This is the one that's got me stuck from moving forward. Using either SysConfig 1.18.0 or SysConfig 1.18.1, when I "LOAD FROM JSON", it returns but there's no changes to the .sysconfig file. As a matter of fact, the .sysconfig file doesn't show as modified in CCS.  I made copies of the sysconfig file before and after loading json files, did a textual diff, no changes. I tried using the json file directly from the SDK folder, didn't make a difference. I made significant changes to the json file and loaded it, not a single change to the .sysconfig file. I'm concluding based on the evidence that the json file isn't being loaded. Is there a SysConfig log file I can look it to see what's happening?

    Here's a snippet of the .sysconfig file -after- loading a json file

    ina3.$name = "CONFIG_INA2";
    ina3.I2CTargetAddress = "0x44";
    ina3.shuntRes = 20;

    mpd_demo1.$name = "CONFIG_MPD_DEMO0";
    mpd_demo1.FLB = "1";

    edma2.$name = "CONFIG_EDMA1";
    edma2.edmaRmDmaCh[0].$name = "CONFIG_EDMA_RM5";
    edma2.edmaRmQdmaCh[0].$name = "CONFIG_EDMA_RM6";

    I feel if I can get this to work, I can make progress in getting a lite build of the Level Sensing demo working.

    BTW: Does anybody know where SysConfig get's the settings needed to generate the ti_cli_mpd_demo_config.h file? I see all the radar settings in there, where did they come from? There's nothing in the .sysconfig file that I see that would relate to these settings.

    Here's a snippet fro the generated header file, where did these FLB settings come from?

    #define FLB_NUM_CHIRPS_PER_BURST 8
    #define FLB_NUM_CHIRPS_ACCUM 0
    #define FLB_BURST_PERIOD 403
    #define FLB_W_BURST_PERIOD (10.0 * 403)
    #define FLB_NUM_BURSTS_PER_FRAME 1
    #define FLB_FRAME_PERIOD ((250.0 * 40000000)/1000.0)
    #define FLB_NUM_FRAMES 0

  • Hello,

    This is an issue that others have reported as well. We have not found the root cause of it yet, but I am able to recreate it and am continuing to look into it. In the meantime, are you trying to upload a default JSON to a default Syscfg as it comes in the SDK? This might be inconvenient but is there a Windows 10 computer you can attempt this on?

    Best Regards,

    Pedrhom

  • No, don't have Win10 machine. I do have a Linux box, would that be a workaround for now?

    My goal is to build the high accuracy level sensing demo from radar toolbox 2.00.00.06, Feature Lite Build, using one of the the chirp configs from the example.

    Goal:

    • C:\ti\radar_toolbox_2_00_00_06\source\ti\examples\Level_Sensing\high_accuracy_low_power_sensors
    • Feature Lite Build
    • high_accuracy_demo_fast_update_xwrl64xx.cfg
    • IWRL6432 ES2 EVM
  • Hello,

    I would try it on the Linux machine if possible, we apologize for the inconveniences. There should be nothing preventing you from having Feature Lite Build be ran on a default setup like that. I will continue to look into this on my end.

    Best Regards,

    Pedrhom

  • I spent a lot of time installing all the tools (CCS, SDK, ToolBox, etc) in my Ubuntu 22.04LTS machine is it behaves the same as on Windows. Loading the JSON file has no effect. BTW, also discovered another bug in the build flow on Linux, I'll create a separate E2E for that one.

    I'm stuck, do you have any kind of ETA when this will be fixed?

    Thanks

  • Hello Brad,

    I am still looking into this, it has been a bit troublesome due to the fact it has been hard to reproduce for those this does not happen to. As it is happening to me as well, I will get back to you the moment I figure something out here.

    Best Regards,

    Pedrhom

  • Hi Pedrhom,

    Any update? Has this been filed as a bug in JIRA and is a fix planned?

    Thanks

  • Hello.

    A JIRA ticket had been filed immediately upon my last message, since as stated prior the bug affects me as well. Several actions have been taken, but I have not heard back in around a week. I just re-pinged those looking into it for a status update and will update here.

    Best Regards,

    Pedrhom