-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
POZYX_ERROR_UNRECDEV #74
Comments
I had the same problem. I was unable to revert to an earlier firmware version with the same symptoms you describe. I wrote to [email protected] and the sent me a special version of the 1.1 firmware that would reset the board. I used my st-link v2 programmer and completely wiped the chip with a full erase. Afterwords I had to use an Arduino Uno and use the pozyx-change-network-id sketch to give the board an id; It was reset to 0x0000. After that I was able to reprogram the chip normally with the proper UWB settings. |
i assume you wiped it using the st-link because dfuse flashing 1.1 followed by 1.3 did not improve things? |
Yes St-Link V2 JTAG programmer. I tried it first with the standard firmware 1.1 and that wouldn’t work. Symptoms were exactly as you described. Laurent sent me a knew firmware 1.1 that was made specially to fix the registers that were changed with the 1.3 version. The tags I flashed with the new 1.1 version after complete erase with the ST-Link and the tags worked immediately with all the LEDs flashing like they used to when communicating. |
thanks for replacing the damaged equipment! however, after spending ~5h trying to get basically anything to work using the windows gui, nothing works as stated, i get all kinds of unrelated and 'unexpected' errors, and i think 'settings don't get written to all the devices in range' with range >= 3m just kinda prevents much success anyway. |
the STM32 is trying to communicate with the DW1000, LEDs 1-4 are active, LEDs 1 and 4 go off for ~125us maybe once per second (seems to happen while the STM32 tries to communicate).
There is activity on all the SPI signals, supply voltages seem ok.
I tried reflashing FW v1.3, which did not help. With v1.1 i don't even get a VCP upon USB connection.
this is a v1.3 anchor.
The text was updated successfully, but these errors were encountered: