DFU upgrades do not complete #1

New Issue

Elara6331 · 2021-08-29T19:20:46Z

Elara6331 commented

2021-08-29 19:20:46 +00:00

When attempting to do a DFU upgrade, the firmware is transferred completely, but then InfiniTime reports an error and the program times out waiting for 0x100301 (DFUResponseRecvFwImgSuccess).

I believe this could be an issue with either step two where the firmware size is sent to the watch or step seven where the firmware is actually transferred. It could be somewhere else, but those are the most likely culprits in my opinion.

When attempting to do a DFU upgrade, the firmware is transferred completely, but then InfiniTime reports an error and the program times out waiting for `0x100301` (`DFUResponseRecvFwImgSuccess`). I believe this could be an issue with either step two where the firmware size is sent to the watch or step seven where the firmware is actually transferred. It could be somewhere else, but those are the most likely culprits in my opinion.

Elara6331 added the

bug

label 2021-08-29 19:21:08 +00:00

Elara6331 referenced this issue from Elara6331/itd

2021-08-29 19:22:37 +00:00

DFU Upgrades do not complete #2

Elara6331 self-assigned this 2021-08-29 19:24:34 +00:00

Elara6331 commented

2021-08-30 16:26:16 +00:00

This is a very strange issue. It's not a hardware issue because this happens on other computers and other companion apps work. It's not a firmware issue because other companion apps work. I have checked using wireshark, and the process appears to be happening correctly, but the watch never sends the required response. Attempting to move on to the next step ignoring the missing response also does not work.

The most confusing part is that the same code worked before. I even tried testing with the initial commit which I know to have worked for sure, and it still did not work.

If anyone has a PineTime to test with, I would appreciate the help as I only have one sealed PineTime.

I will try to let the PineTime's battery die and then recharge and test just in case, but otherwise, I will keep trying to see if I can identify an issue in the code.

This is a very strange issue. It's not a hardware issue because this happens on other computers and other companion apps work. It's not a firmware issue because other companion apps work. I have checked using wireshark, and the process appears to be happening correctly, but the watch never sends the required response. Attempting to move on to the next step ignoring the missing response also does not work. The most confusing part is that the same code worked before. I even tried testing with the initial commit which I know to have worked for sure, and it still did not work. If anyone has a PineTime to test with, I would appreciate the help as I only have one sealed PineTime. I will try to let the PineTime's battery die and then recharge and test just in case, but otherwise, I will keep trying to see if I can identify an issue in the code.

Elara6331 added the

help wanted

label 2021-08-30 16:27:10 +00:00

Elara6331 commented

2021-09-01 06:38:49 +00:00

I have found the bug. It does not seem to be in the program itself, but somewhere in the environment. Particularly, it seems to have started after updating my computer. Both my computers run Arch, so testing on both of them yielded the same issue. I tried on my PinePhone and it worked perfectly. I don't know exactly what program has this bug, so I will leave this open as I try each program and see which one is responsible.

Elara6331 removed the

help wanted

label 2021-09-01 06:38:55 +00:00

Elara6331 commented

2021-10-07 00:25:30 +00:00

I tried downgrading each package and that didn't help. I ultimately narrowed it down to either a hardware or firmware issue. I could not even get the recovery firmware to load. I then bought a new PineTime, and it arrived today. It is getting reliable DFU updates, so I believe I can now close this issue.

Elara6331 closed this issue

2021-10-07 00:25:55 +00:00

This repo is archived. You cannot comment on issues.