• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 31 subscribers
  • Views 332 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.

IWR6843AOP: Can't start sensor

Lewis Barclay
Prodigy 10 points
Part Number: IWR6843AOP


Hello,

I am have made a prototype board of the IWR6843AOP and seems to work. I can't yet view the output from the sensor as I don't have code for using a single UART yet (I only have one UART on the board), but I tested some of the example codes and they flash fine, but when I send the config to the device, the LED does not come on after start. So I tried the "Hard Code config" example and I get the below logs repeating hundreds of times every second, is this normal? It seems like the sensor can't start but there is no error:

******************************************

Wait some time for system to initialize...

Performing hard-coded config

mmwDemo:/>Command

Ignored: Sensor is already stopped

Done

mmwDemo:/>Command

Done

mmwDemo:/>Command

Done

mmwDemo:/>Command

Done

...

Done

mmwDemo:/>Command

******************************************

xWR68xx MMW Demo 03.05.00.04

******************************************

Wait some time for system to initialize...

Performing hard-coded config

mmwDemo:/>Command

Ignored: Sensor is already stopped

Done

mmwDemo:/>Command

Done

mmwDemo:/>Command

Done

...
mmwDemo:/>Command

Done

******************************************

xWR68xx MMW Demo 03.05.00.04

******************************************

Wait some time for system to initialize...

Performing hard-coded config

mmwDemo:/>Command

Ignored: Sensor is already stopped

Done

mmwDemo:/>Command

Done

mmwDemo:/>Command

Done

...

  • 0
    TI__Mastermind 20860 points

    Hello.

    Can you please send your hard-coded configuration?  And make sure you have followed the steps in the developer's guide section in the Hard Coded Config User Guide in the radar toolbox?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 10 points

    Hello!

    I was using the prebuilt binary folder from the hard-coded config example to test this and these were the results from the configuration UART port. Is this the expected result? To me it seems like the sensor isn't starting for some reason

  • 0 in reply to Lewis Barclay
    TI__Mastermind 20860 points

    Hello.

    I think you may be connected to the incorrect com port.  I can double check the behavior on the UART port, but have you tried connecting to the data port and seeing what data is being streamed out of the device?  That will indicate whether the radar is actually running/the sensor was starting.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 10 points

    Hi Santosh,

    Our board design only incorporates a single UART port, is there any example we can test with a single UART?

  • 0 in reply to Lewis Barclay
    TI__Mastermind 20860 points

    Hello.

    Since you are using the hard-coded configuration, you no longer need to use the UART port to send configuration commands.  You could instead stream the TLV data from the device to the UART port and read via a serial terminal.  However, since this is a custom board, would this be possible?  We currently do not have any examples for using a single UART port, but if you had access to a 6843AOP EVM, you could try applying some of the suggestions mentioned here and translate it to your custom board. 

    With regards to the functionality of the demo, have you tried running the HCC on one of our 6843AOP EVMs?  You can go through the developer's guide to understand how the demo is working and try modifying it to utilize only one UART port as the demo is most likely set up to use two, and then flash that modified image onto your board.  Finally, another thing you can try to determine if your sensor is working is rather than use the UART COM port to send in data, use that port to output UART data from the device.  Since you no longer need to send in configuration commands due to using HCC, you can simply output the data to the UART, and if it is not starting, no output will be displayed on the terminal.  

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 10 points

    Hi Santosh, thanks I will try the suggestions, we do have an EVM so I can try it on that board first to get it working then translate it over.

    The other thing I was thinking is on our custom board, I do have two GPIO pins exposed. Can I change the code over to use one of the GPIOs? One I have free is GPIO44, is it possible to use that pin as TX for the logging UART?

    I tried it last night but didn't get any output - I'm not sure if this is because the pin can't be used as a UART (the datasheet doesn't say it's a UART pin) or if it's because the sensor isn't starting

  • 0 in reply to Lewis Barclay
    TI__Mastermind 20860 points

    Hello Lewis.

    I'm not sure how much useful data you would get from the GPIO as it would only output a high or low signal.  Perhaps you could you use it as an indicator for when you are streaming data from the radar device to your computer.

    Sincerely,

    Santosh