Part Number: CC1311R3
Hi,
We see a strange behavior that we have been struggling with for days.
The chip basically stops working after RF_Open is called the first time.
The next command - RF_runCmd(RFHandle, (RF_Op*)RFPublic.CMD_fs_rx, RF_PriorityNormal, NULL, 0);
never returns.
A UART printout between RF_Open and RF_runCmd send out garbage on UART. So obviously something is not good inside the chip.
- We have check the parameters of the RFOpen and replaced with ones copied from SmartRFstudio -> Did not help
- We have check the stack and it has plenty of space.
- This is all run in task context, so only only the specific thread halts..
I just want to have some brainstorming from support on what can cause the RF_Open command to break the system in such matter.
- no_more_wires
