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

CCS/IWR1443: debugging and binary building

allen dominek
Expert 1515 points
Part Number: IWR1443
Other Parts Discussed in Thread: TMS320C6748, UNIFLASH

Tool/software: Code Composer Studio

Hi,

I would like to use CCS to debug the OOB Demo.  I loaded xxwr12xx_xwr14xx_radarss.bin and wr14xx_ccsdebug_mss.bin into the part and started a debug session.  My question is how do I provide the configuration data that the demo visualizer would?

I have also built the mss binaries for the oob demo and high accuracy apps but I can not get them to run when loaded.  The prebuilt binaries do.  The binaries are comparable in size to  the prebuilt binaries for what it is worth.  When I load a configuration file when a prebuilt binary is loaded, I can observe data exchanging by  cat /dev/ttyACM0 or /dev/ttyACM1.  The first port has

version
Platform          : xWR14xx
mmWave SDK Version: 01.02.00.05
RF H/W Version    : 02.00
RF F/W Version    : 02.00.00.15.18.01.11
mmWaveLink Version: 01.00.00.00
Done

SDK v
with nonascii data on the other port.   When a binary that I made is loaded, only

version

is shown on /dev/ttyACM0 with no data on the other port.  How can I debug this to find out what I am doing wrong? No errors or warnings are being generated during the build process.

One side question.  I use to get statistics displayed in the profiling window but recently, only the platform and sdk version is displayed.  Any thoughts on what happened to this data?  When the options of chirp/frame or scene is choosen, data is displayed.

Thanks.

Al

  • 0
    Expert 1515 points

    Hi,

    I have been able to partially answer my first question but not completely.  I found two documents referring to ccs debugging.  One was 6153.mm_user_guide.pdf and the other ADC Data Capture SDK1.05 V1.00.pdf.  The first one provided guidance on how to connection/load and run followed by gui control.  The second document indicated ccs debugging with configuration through serial program (I used minicom).

    Through minicom, I was able to supply parameter and start the part on /dev/ttyACM0 and recover data on /dev/ttyACM1.  However, I was unable to obtain ccs console feedback that the CLI was operational.  I have attached three images.  The first two are from my ccs session and the third image is from the 6153 pdf source to illustrate that I did not end up with an operational CLI.  Can you please provide some guidance to me on this?

    My issue with not being able to build functional binaries still exists even though no errors or warning were generated during the build.  I could not provide configuration information via the gui or the serial port as I did above.  I would appreciate some guidance on this.

    Strangely, I am now able to render the timing statistics in the gui that I was not earily.  Go figure.

    Al

  • 0 in reply to allen dominek
    TI__Guru 50240 points
    Hi Allen,

    It appears that you are running the Water/Ground Demo. After the "CLI is operational" command appears you should be able to freely run the demo through the GUI. Have you tried this? If unsuccessful would you be able to post a screenshot of the Matlab Console and whatever error messages might be happening?


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Expert 1515 points

    Hi Akash,

    I am sorry for sending this posting.  I had resolved my issue with the debugging side and I replied to it and indicated the "This resolved my issue".  I was not running the water/ground demo but that is the user guide I looked at.  I was should have looked at the actual user guide fo r the software I was working on since that document closely match what I was observing.

    I do have an issue with building a binary though.  I made a new posting under "CCS/IWR1443: mmwave build problem with ccs".  (e2e.ti.com/support/sensor/mmwave_sensors/f/1023/t/726639)

    I am repeating here for your convenience.  

    Hi,

    I built the oob demo for a iwr1443 board using CCS 7.4 on a linux platform.  The SDK version was 1.2.0.5.  I loaded the binary in the part using uniflash  version 4.4.  It did not run so I attempted a debug session with CCS.  I had no build errors or warnings during the build process.  I can load other prebuilt binaries and they run fine.  I have attached a screen image of the debug session.  It can not find a file from a /tmp/scratch/build_jenkins/.... location I do not have.  I searched for assistance on the forum pertaining to the missing file and found this posting: CCS/TMS320C6748: ccsv5.5 - can't open time.h and rand.h.  This old posting does not provide any assistance to me.

    Please advise.  Thanks.

    Al

  • 0 in reply to allen dominek
    TI__Guru 50240 points
    Hi Allen,

    It appears Nitin was able to resolve your query in a separate thread so I'm going to close this one. If you have more questions feel free to open up a new one!


    Cheers,
    Akash