According to pcap-diff the packages seem to be the same:
╭─mashuptwice@yoga ~/github/pcap-diff ‹master›
╰─$ ./pcap_diff.py -i ../../pinetime_itd_success.pcapng -i ../../pinetim…I'll start a session with wireshark, will report back the results.
Sounds like something funky is going on. That means I also don't need to check for differences in the files manually..
If you want to run ITD with your modified infinitime library, you can add replace go.arsenm.dev/infinitime => /path/to/infinitime into the go.mod file.
Thanks, that'll save me from using…
Thanks for the explanation, I appreciate it!
I'll try to add a routine into your infinitime library which writes the contents of the zip file to a local folder, to identify the exact differences…
Considering the painfully slow upgrade procedure on my machine and considering that infinitime already does that at the end of the transfer by itself, I don't see the benefit of a CRC check at the…
Well, the manifest contains a CRC16 checksum of the firmware. After having a look over infinitime/dfu.go, it seems (I don't know anything about go) that there is no check if the firmware file…
Should I open an issue on the library repo instead? If I understand correctly, `func (c *Client) FirmwareUpgrade(ctx context.Context, upgType…
Good point, but I think I've already tested that. I've compressed the firmware with zip -9 and it fails again.
Yeah, my bad, seems like I had an older compiled version of itctl, unmanaged by my package manager. Sorry for that, I don't know how I could've missed that.
I think it would be useful to also…
Please re-read the issue.
╰─$ itctl res load
No help topic for 'res'
╰─$ itctl resources load
No help topic for 'resources'
╰─$ itd --version
0.0.9