Thanks much egnor. Yes, referring to the SFD timeout. I don’t suppose you’d be willing to share your SS ranging code? The code I’m using is from the SS example as part of the Decawave API, located here: “\dw1000_api_rev2p14_stsw\dw1000_api_rev2p14_stsw\Src\examples\ex_06a_ss_twr_init” and ex_06b_ss_twr_resp, so you can see exactly what I’m doing. These are the register values as best I can tell from your brief descriptions:
regval = dwt_read32bitreg(SYS_CFG_ID);
regval = dwt_read32bitreg(TX_FCTRL_ID);
regval = dwt_read32bitreg(CHAN_CTRL_ID);
regval = dwt_read32bitreg(DRX_CONF_ID+DRX_TUNE0b_OFFSET);
regval = dwt_read32bitreg(DRX_CONF_ID+DRX_TUNE1a_OFFSET);
regval = dwt_read32bitreg(DRX_CONF_ID+DRX_TUNE1b_OFFSET);
regval = dwt_read32bitreg(DRX_CONF_ID+DRX_TUNE2_OFFSET);
regval = dwt_read32bitreg(RF_CONF_ID);
regval = dwt_read32bitreg(DRX_CONF_ID+RF_TXCTRL_OFFSET);
//RX_CAL_RESI not found
//RX_CAL_RESQ not found
The ID’s are pulled directly from deca_regs.h, I could not find any register matching the last two descriptors, if you can give me their ID’s (register address) I can get you those as well. Here are the values in order:
0x00001200
0x00164000
0x4a480022
0xdeaddead
0xe7550448
0x00000000
0xdeadde00
0x00000000
0xdeaddead
I certainly believe that given the insane number of registers and settings involved, but what I don’t understand is why the reference code from Decawave doesn’t seem to work, building the code from scratch not knowing the intricacies of the chip seems untenable and unnecessary. Do you work for Decawave? If not, they haven’t contributed to this thread at all. Thanks very much for your help.