Other Parts Discussed in Thread: UNIFLASH, IWRL6432,
Tool/software:
Hello!
I am exploring the 6432AOP and running some of the pre-built images and the visualizers, while a bit quirky, does work eventually. I have been using the Vital Signs demo and it's prebuilt appImage. I wanted to start working with the code so my first step was to just push what I believe to be the exact same code from https://dev.ti.com/tirex/explore/node?node=A__AS5.DPBhh5hqkLB3.kAODg__radar_toolbox__1AslXXD__LATEST&placeholder=true
I followed these steps:
- I imported the project into the cloud CCS
- Compiled it in release mode
- Downloaded the vital_signsxxxx.out file
- Used out2rprc to convert the .out to a .rprc
- Used multicoreimagegen to convert that to an .appImage
- Used crcMultiCoreImage to calculate the crc
- Used appendBinCrc to append it
- Used uniflash to upload the image.
All of that seemed to work. When I connected the visualizer to it, it seemed to freeze, however looking at the console behind it, it was feeding it the chirp config SLOWLY line by line, took about 1 minute, then just basically errored out.
I am not exactly sure what I did wrong and am hoping it is something obvious. I did not see the AOP version of the chip listed as a device in CCS, just the IWRL6432 I am not sure if that matters, I assumed the chirp config handled much of the differences. Complicating some things I am on a MacBook M4, but doing most of these steps in Parallels in Windows 11 Arm.
As a note, I don't think the drivers for the USB XDS110 work on Windows 11 Arm 64bit. I can talk to it over UART, but I think not running stock windows x86-64 if complicating things.
Lastly, I noticed more files that seemed to be pulled into the Cloud CCS version of the code, but they appear to be SDK related (and I do see things like mmw_cli.h that seem to be includes) I am assuming the cloud CCS is just pulling them in given it has to package it differently.
Anyway - I hope this is enough detail.
