• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 135 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Board not responding, unable to flash

Adam Koutny
Intellectual 410 points
Part Number: IWR6843AOP
Other Parts Discussed in Thread: UNIFLASH,

Hi, I am currently working with a custom board based on the IWR6843AOP, for which I have modified the out-of-the-box firmware to include CAN-FD communication and a hard-coded configuration. I successfully tested receiving data over CAN and sending commands to start/stop the sensor via CAN. However, the board has recently become unresponsive and I am unable to reflash it using Uniflash. Here are the changes I made to the firmware prior to encountering these issues:

  1. I modified the CLI_task to process commands received over CAN, while disabling UART_read as I do not intend to use UART in this manner.

  2. I experimented with various hard-coded configurations, including one recommended on a ROS forum, which suggested using the maximum chirp bandwidth.

  3. I encountered a "HWI Stack Overflow" error in MmwDemo_sensorStopEpilog() during the implementation of the start/stop functionality over CAN. Despite efforts to resolve this by simplifying the code and removing unnecessary variables, the issue persists.

I have verified the voltage at my test points, which suggests that the hardware on my custom board may not be the problem.

I would appreciate your insights on the following:

  1. Could the stack overflow issue be causing the board's unresponsiveness?

  2. Is there a way to reset the IWR6843AOP to a default state?

  3. Could the modifications I made to the firmware be disrupting the image flashing process?

Thank you for your assistance.

Best regards,

Adam