Tried both 1.0 and 1.1 variants on my T-Deck Pro (4G).
It doesn't boot into anything and USB connection is cycling (infinite connect-disconnect loops)
(Tested on full 4G-BLE-merged version)
Tried both 1.0 and 1.1 variants on my T-Deck Pro (4G).
It doesn't boot into anything and USB connection is cycling (infinite connect-disconnect loops)
(Tested on full 4G-BLE-merged version)
<!-- github-sync-id:4092967985 -->
Tried both 1.0 and 1.1 variants on my T-Deck Pro (4G).
It doesn't boot into anything and USB connection is cycling (infinite connect-disconnect loops)
(Tested on full 4G-BLE-merged version)
Hello! Apologies, GitHub didn't email me automatically as usual so only just spotted your post. Not sure if you were the same user on Discord who was talking to me about the issue, but it's one I'm currently investigating.
The current (temporary) fix for the issue is to select Ripple firmware on the Meshcore.co.uk web flasher first and do an erase flash - for example, select 'Ripple GUI: data on SD card (T-Deck Pro v1.1)', tick erase device, and flash. And then go immediately right back to the main flasher page and to the Custom Firmware option to flash with an unmerged Meck v1.1 firmware bin file without erasing.
It may be something in the way the script builds the merged files that's interfering with the builds, am looking into it.
Let me know if that fix works for you for now.
> Tried both 1.0 and 1.1 variants on my T-Deck Pro (4G).
> It doesn't boot into anything and USB connection is cycling (infinite connect-disconnect loops)
> (Tested on full 4G-BLE-merged version)
Hello! Apologies, GitHub didn't email me automatically as usual so only just spotted your post. Not sure if you were the same user on Discord who was talking to me about the issue, but it's one I'm currently investigating.
The current (temporary) fix for the issue is to select Ripple firmware on the Meshcore.co.uk web flasher first and do an erase flash - for example, select 'Ripple GUI: data on SD card (T-Deck Pro v1.1)', tick erase device, and flash. And then go immediately right back to the main flasher page and to the Custom Firmware option to flash with an **unmerged** Meck v1.1 firmware bin file without erasing.
It may be something in the way the script builds the merged files that's interfering with the builds, am looking into it.
Let me know if that fix works for you for now.
<!-- github-comment-id:4091415498 -->
Nope, it was someone else.
Thank you, this workaround seemingly helped. I think we should leave this issue to help others until this is resolved.
BTW, cool firmware!)
Nope, it was someone else.
Thank you, this workaround seemingly helped. I think we should leave this issue to help others until this is resolved.
BTW, cool firmware!)
<!-- github-comment-id:4096638215 -->
after hours of debugging and absolutely doing my head in trying all sorts of weird and complicated fixes with Claude AIs help.....
it turned out the real issue was using underscore instead instead of dash in the merged files filename. 🙃
Issue occurred because I hadn't realised the meshcore.co.uk web flasher is gated to only recognise the - in merged filenames, hence the underscore causing some sort of weird corruption.
after hours of debugging and absolutely doing my head in trying all sorts of weird and complicated fixes with Claude AIs help.....
it turned out the real issue was using underscore instead instead of dash in the merged files filename. 🙃
Issue occurred because I hadn't realised the meshcore.co.uk web flasher is gated to only recognise the - in merged filenames, hence the underscore causing some sort of weird corruption.
In any case, good opportunity for Meck v1.2 release! @Unb0rn please let me know if the v1.2 files work in the web flasher for you: [https://github.com/pelgraine/Meck/releases/tag/v1.2](https://github.com/pelgraine/Meck/releases/tag/v1.2)
<!-- github-comment-id:4097184633 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Tried both 1.0 and 1.1 variants on my T-Deck Pro (4G).
It doesn't boot into anything and USB connection is cycling (infinite connect-disconnect loops)
(Tested on full 4G-BLE-merged version)
Hello! Apologies, GitHub didn't email me automatically as usual so only just spotted your post. Not sure if you were the same user on Discord who was talking to me about the issue, but it's one I'm currently investigating.
The current (temporary) fix for the issue is to select Ripple firmware on the Meshcore.co.uk web flasher first and do an erase flash - for example, select 'Ripple GUI: data on SD card (T-Deck Pro v1.1)', tick erase device, and flash. And then go immediately right back to the main flasher page and to the Custom Firmware option to flash with an unmerged Meck v1.1 firmware bin file without erasing.
It may be something in the way the script builds the merged files that's interfering with the builds, am looking into it.
Let me know if that fix works for you for now.
Nope, it was someone else.
Thank you, this workaround seemingly helped. I think we should leave this issue to help others until this is resolved.
BTW, cool firmware!)
after hours of debugging and absolutely doing my head in trying all sorts of weird and complicated fixes with Claude AIs help.....
it turned out the real issue was using underscore instead instead of dash in the merged files filename. 🙃
Issue occurred because I hadn't realised the meshcore.co.uk web flasher is gated to only recognise the - in merged filenames, hence the underscore causing some sort of weird corruption.
In any case, good opportunity for Meck v1.2 release! @Unb0rn please let me know if the v1.2 files work in the web flasher for you: https://github.com/pelgraine/Meck/releases/tag/v1.2
Woah, that was quick. Yeah, merged firmware seems to be working now, thank you!