FDD_EXIT_COND and IDM_CLR behaviour #1
Description
Here is something interesting that I found out about the FH101RF in case somebody else stumbles upon this:
I was trying to use the FDD_EXIT_COND register to debug why I was not getting ID matches, since it tells you the reason why the device exited FDD mode.
As it turns out, it was always 0 when I tried to read it, which makes no sense since it was entering FDD for sure as indicated by FDD_ACTIVE (which btw is wrongly documented or something weird is happening because it tells me 2.4GHz is active but I have that one disabled for ID matching and also I'm able to decode IDs in the correct frequency).
As far as I can tell, the issue is that whenever you clear FDD_EXIT_COND by writing 1 to IDM_CLR as stated in the documentation, FDD_EXIT_COND will never by anything other than 0 again until you power cycle the device. This was also the case with the dev kit so I don't think it is an issue with the driver. I also tried writing 0 to IDM_CLR but that did not help.