AWR1443: MSS binary for capture demo

Hi Kyle,

Can you tell us how can we find which silicon version do we have?

Thanks,

Hi Cesar,

I have looked at the folder which you have mentioned but did not follow what you want me to do next.

Can you take a look at this thread e2e.ti.com/.../2412525 ?

This e2e thread mentions about a MSS binary and some commands which we can run from a serial port to put the device in CW mode. I am looking for the binary and the commands.

Thanks

Hi Cesar,

We tried SDK 1.2.0.5 and this is supposed to work with AWR1443 ES2.0 as mentioned in the release notes. Please check the error logs we are seeing while flashing the binaries.

[3/6/2019, 3:29:02 PM] [INFO] Cortex_R4_0: Flashing process starting...

Thanks

Thanks Kyle,

We will double check this.Can you comment on how can we find out which version of silicon do we have?

Thanks,

Hi Kyle,

See attached the Uniflash configuration where we have BSS as the first entry and MSS as the second entry. Still the uniflash tool throws an error.

We have tried with both SDKs 1.2.0.5 (supposed to work with 1443 ES2.0) and 2.1.0.4 (supposed to work with 1443 ES3.0). Please suggest the next steps so that we can use TI board.

We had purchased the TI AWR 1443 board in Nov-Dec 2018. Can you suggest how can we identify the ES version we have? I am also attaching a picture of our board in case you want to see it.

Thanks

Thanks Kyle. We are able to flash the MSS binary. Can you tell us the minimum set of commands needed to put the device in CW transmission mode say at 77 GHz?

We tried the following commands as per thread  but were not successful

flushCfg
dfeDataOutputMode 2
channelCfg 2 1 0
adcCfg 2 2
adcbufCfg 0 0 1 1
lowPower 0 0
contModeCfg 77 0 0 8000 0 0 30 1 1024
setHSI LVDS ADC disable
sensorStart

Thanks,

Kyle,

It took me some time for me to figure out that you are referring to Table 1 in SDK user guide document. Anyways, thanks.

I do not see any mention of contModeCfg in the table that you have mentioned.

I am sure you would agree that to put the device in continuous transmission (fixed frequency at say 77 GHz) mode, we do not need chirpCfg, frameCfg. But these commands have been mentioned as mandatory in the table that you have referred to.

There is a command called contModeCfg which is hooked to the CLI_MMWaveContModeCfg handler but the error check indicates that if DFE output mode is not CONTINUOUS then this command would not work. Please see the code snippet below.

Table 1 in SDK user guide says that in 1443, dfeDataOutputMode only frame based chirps (i.e. only option 1) is supported in 1443.

Do we need to modify the application? If yes, please send us the instructions to do so.

Can you help us with the minimum set of commands to put the device in continuous transmission mode?

Thanks,

Hi Kyle,

We do not have a DevPack with us nor do we have a DCA1000 capture card. If you have ideas on how we can use MMWAVEStudio without these intermediate cards with AWR1443 ES3.0 EVM, please send us the instructions.

If the answer to the above is in negative, please send across the instructions to enable continuous transmission using 2.1 SDK. If you already have the binary built which has been tested (make sure it is only an 1443 EVM and no DevPack nor DCA1000), I can use that as well. Make sure that using CLI command we should be able to change the CW transmission frequency.

Did you look at the e2e thread 

which has clear instructions on how to use CW transmission mode using SDK? I need similar instructions with SDK 2.1 on AWR1443 ES3.0 EVM.

Thanks

Hi Kyle,

Firstly, CW mode testing will be done on all production devices.

Secondly, CW mode was introduced by TI in SDK 1.1? Is it that TI realized only recently that 1443 is a FMCW radar device and hence this was removed in SDK 2.1?

Thanks,