IWR1843BOOST: IWR1843BOOST

Hi,

You will not be able to debug both projects at the same time because the MSS runs on the ARM core and the DSS on the DSP core. 

What are you trying to debug?

Thank you

Cesar

Currently just trying to debug MSS.  To do so, however, I need for the DSS subsystem to be running.  Just not sure how to make that happen with CCS.

Both the MSS and DSS code are organized in threads.

One can put a breakpoint in a thread. At that point one should still be able to step through the code in that thread.

For debugging we also recommend setting frame_numer =1. In this way there are no additional frame start interrrupts for the following frame.

Thank you

Cesar

I am very new to this development environment and these TI EVM modules, so apologies if these questions are very rudimentary.

My problem seems to be that when I start debugging from the run menu in CCS, it seems to only start the selected project (either mrr_18xx_mss or mrr_18xx_dss).  If I start dss and then attempt to start mss, I get the error "A Code Composer Studio debug session is in progress, press the Continue button to terminate it and continue with tstartin a new debug session."

How do I initiate a debug session that launches both applications?  

Also, not finding anything in the demo code for "frame_number".  Where do I adjust this?

Thank you,

Ron

Hello,

which ccs version are you using?

Best,

Gigliotti

Version: 20.0.2.5__1.6.2

Please try version 12.x, I use 12.8 and that should cause no issues. Let me know if that works.

Really?  That is quite the jump back and we haven't even tried to understand why 20.0 isn't working.  How should it work?  Or is it just known not to work with my use case?

Can you please provide a download link for 12.x?

I have installed CCS v12.8.1.00005 and have been able to build the Medium Range Radar MSS and DSS projects.  I am able to start them both in the debugger.  However, I am not getting any data on the MMR Visualizer when running via the debugger.  If I flash xwr18xx_mrr_demo.bin and run in functional mode (dip switches set to SP2: Off, SP1: Off, SP0: On), then I do get data on the MMR Visualizer.  So, the issue seems to be something about they way I am launching the application via the debugger. 

Here is the CIO output...

[C674X_0] [Tue Mar 4 16:33:11] Heap L1 : size 16384 (0x4000), free 6144 (0x1800)
[Tue Mar 4 16:33:11] Heap L3 : size 1048576 (0x100000), free 0 (0x0)
[Tue Mar 4 16:33:11] Heap L1 : size 16384 (0x4000), free 1000 (0x3e8)
[Tue Mar 4 16:33:11] Heap L3 : size 1048576 (0x100000), free 262144 (0x40000)
[Tue Mar 4 16:33:11] Heap L2 : size 102400 (0x19000), free 21488 (0x53f0)
[Tue Mar 4 16:33:11] Heap L2 : size 102400 (0x19000), free 14432 (0x3860)
[Cortex_R4_0] [Tue Mar 4 16:33:23] RTC: Launched the Initialization Task MRR_MSS_initTask
[Tue Mar 4 16:33:23] Debug: Initialized the mmWave module
[Tue Mar 4 16:33:23] Debug: Synchronized the mmWave module
[Tue Mar 4 16:33:24] Error: Asynchronous Event SB Id 16 not handled

The key error seems to be "Error: Asynchronous Event SB Id 16 not handled", whatever that means.  I get the error regardless of which application (mss or dss) I start first.

Thoughts?

Thank you,

Ron

If I remember correctly, you have to group together the two cores in CCS. 

Select both cores and group them together. From there load your respective images. Once both images are loaded click on the group name and press play. This will ensure that they start at the same time.

Best,

Gigliotti

How do I navigate to the menu where I can get to the "Group core(s)" menu item?  I have two projects, as shown in attached screen shot,  but can't see the cores for the target device.  Where do I find the cores to select?

Ok, thanks.  I had given up on that guide when I was using CCS 20.  Hopefully more success now with CCS 12.
One thing, though.  Looks like you are referencing version 3.0.0.0 of the Radar Toolbox.  Highest version I see online is 2.30.00.12.  Should I be using 3.0?

Thanks!

Ron

One thing that is not clear from the users guide is what mode the module should be place in after flashing the xwr18xx_ccsdebug.bin.  Should it be put in functional mode so that the bin is executed?  Or put in debug/development mode?  I am not understanding why the cssdebug bin file is needed, since I can connect, download and run (to some degree) without it when in development mode.

So, by putting the module in functional mode and rebooting it, seems I am able to launch both cores per the user's guide.  The " Asynchronous Event SB Id 16 not handled." looks to have gone away.  However, I am not seeing any output on the MMR Visualizer.  Should I be able to see output on the MMR Visualizer?

Ok so once you flash the ccs debug bin you then must place the board in functional mode. It is then "running" this image which is just waiting for you to load the application via CCS as explained in the user guide. So are you reloading the images as explained in the user guide? Grouping the cores and loading the respective cores etc.

Yes, I am loading and running with CSS v12 per the users guide.  I am seeing the "MMWave has been configured for MRR” and "Sensor will start momentarily” messages as expected, and no error messages.  Thoughts?

Also, for learning more about how this development environment works, why is the ccsdebug.bin used with EVM in functional mode rather than just launching the applications directly with the EVM in debug/development mode?

Yes it seems the sensor is now working correctly. Did you try the visualizer then make sure you inputted the correct data port? Another verification method is using a serializer like tera term where you can see if data is being outputted at least from the data port. To see the function of each SOP mode I would refer to TRM(technical reference manual) that should provide a detailed purpose of each mode. I have not worked in debug/development mode ever.

Yes, the visualizer always uses COM5 in my setup.  

Only description I have found for the IWR1843BOOST module for the SOP settings is section 2.8.1 of the user's guide.  It specifies the dipswitch settings for each mode but doesn't explain why I would use ccsdebug.bin in functional mode verse just running with debug mode.

I verified that I can see serial data with tera term when the applications are flashed.  When running via ccsdebug.bin, I do not see any data with tera term.  Here is the console output...

[Cortex_R4_0] RTC: Launched the Initialization Task MRR_MSS_initTask
[C674X_0] Heap L1 : size 16384 (0x4000), free 6144 (0x1800)
Heap L3 : size 1048576 (0x100000), free 0 (0x0)
[Cortex_R4_0] Debug: Initialized the mmWave module
[C674X_0] Heap L1 : size 16384 (0x4000), free 1000 (0x3e8)
[Cortex_R4_0] Debug: Synchronized the mmWave module
[C674X_0] Heap L3 : size 1048576 (0x100000), free 262144 (0x40000)
Heap L2 : size 102400 (0x19000), free 21488 (0x53f0)
[Cortex_R4_0] Set LDO Bypass
[C674X_0] Heap L2 : size 102400 (0x19000), free 14432 (0x3860)
[Cortex_R4_0] Debug: MMWave has been configured for MRR.
RTC: The sensor will start momentarily.
RTC: Running Status is TRUE.
RTC: Initialization Task MRR_MSS_initTask complete.

(Note, I added my initials as a prefix to some of the messages to verify it was actually running the code that I built)

I really could use some help troubleshooting this problem.
Thank you!
Ron

I have some new information that might be of help here.  I have configured the CLI to NOT automatically initialize advFrameCfg and start the sensor.  I have flashed this application to the 1842 BOOST EVM.  Application boots fine and I can get the sensor running by issuing the "advFrameCfg" and "startSensor" commands.  I get good output on the MRR Visualizer.  While the application is running, it is continuously collecting data in the background.  The application runs fine for extended periods of time without problem while collecting data.   However, when I request a dump of the data via the CLI (via a custom command), the data gets dumped fine but the sensor then stops.  Evidently something with the CLI has the potential to interfere with the sensor?  Attempts to "stopSensor" and "startSensor" do not get the sensor unstuck.  Thoughts on how to trouble shoot?