Dear all,
During the porting from s113 to s140 I lost ranging capability. Even if I rollback to old s113 ranging doesn’t work anymore. I started from QANI example. Do you know how to recover the calibration parameters or how to check them ? Is there a sort of script to use?
thanks a lot.
Can you try to use the UCI firmware and use the load_cal UCI script to load the calibration for the Type2AB EVB?
load_cal script can be found here: DW3_QM33_SDK_1.1.1\SDK\Tools\uwb-qorvo-tools\scripts\device\load_cal
calibration for Type2AB_EVB antennas can be found here: DW3_QM33_SDK_1.1.1\SDK\Tools\uwb-qorvo-tools\scripts\device\load_cal\calib_files\Type2AB_EVB\patch_aoa.json
Hi Akash,
I donw thave DW3_QM33_SDK_1.1.1\SDK\Tools\uwb-qorvo-tools. Do you know where to download ?
I can flash of course UCI firmware on the board
Awaiting your help
Thanks
What sdk are you using? 1.0.2 has the scripts as well
See here for link to request access to sdk via download
https://www.qorvo.com/products/ek/DWM3001CDK
1 Like
Hi Rexadd,
i was able to find it in 1.1.0 .
Anyway Im having a lot of problem in fira ranging.
I will open another thread on that since it seems tha fira ranging stop to work; after some period of time report_cb() callback stop to run.
Thanks,
Nicola
Is this twr, uci or cli?
Someone else reported controller side stop reporting
In my BLE addition to uci, I had a problem with Fira routine heap allocation failure during ranging startup, which caused no ranging reports altho ranging was running.
I had to shuffle some heap allocations to static variables
I had to add the Nordic heap watch routine to catch it
Did you /can you use twr to load the config to the boards
I started from QANI (s113) cause I needed ble in parallel with twr. I disabled all my custom tasks and also the ble_init and left just QANI task running, the task correctly runs so freertos is not blocked as also the firmware (I put some counters inside the qani_task and they work) and I saw that the report_cb callback is not notified anymore after 10 minutes . So im putting some watchdog to call stopUWB and StartUWB again. The firmware is running.
Don’t know why to be honest.
I extended the QANI package for some extra BLE support so I know that works