Closed cybernesto closed 2 years ago
It's the other way around. The latest RC is using DFU, and that will be the type used for the next stable version. The wiki was updated in preparation for that, and honestly you should be using the latest RC as it is considered stable, i have been using it for a few weeks now since it came out. It has a lot of PD fixes, menus work better and screen updates are faster.
Thanks for the clarification. Maybe a short notice stating that the DFU mode is only supported by the current RC would avoid issues.
cybernesto
Am 24.12.2021 um 23:37 schrieb John Norrbin @.***>:
It's the other way around. The latest RC is using DFU, and that will be the type used for the next stable version. The wiki was updated in preparation for that, and honestly you should be using the latest RC as it is considered stable, i have been using it for a few weeks now since it came out. It has a lot of PD fixes, menus work better and screen updates are faster.
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.
@Ralim Is anything missing to push out a new stable release? The latest RC has been working amazing for me for a long time now.
I just tried the RC2: V2.16. Flashing worked as documented. Thanks for the hint. I have found one flaw though. With v2.15 I was able to use up to 12V in QC mode from my power supply. The RC2 only offers 5V. Changing the power settings does not help. Is this a known issue?
@cybernesto Please create a new issue for issues with QC for your specific charger. Make sure to include details on what firmware you were using before and what model your charger is so that it can be checked if its QC3 or QC2 certified or not certified at all.
QC is NOT RECOMMENDED due to it being terribly implemented by different chargers, and only just meeting the minimum 12V voltage.
Still some niggling issues to sort out in settings refactor and then ill be releasing it
Closing this issue since the flashing instructions refer to the dfu files included in the RC. A comment about this would be nice though.
Intent is that you read the instructions that match the file you download.
You can click the version tag (starts with v
) next to the release to view the data matching that release.
Brilliant. I was not aware of this feature. Thanks for the hint!
Am 29.12.2021 um 09:59 schrieb Ben V. Brown @.***>:
Intent is that you read the instructions that match the file you download. You can click the version tag (starts with v) next to the release to view the data matching that release.
— Reply to this email directly, view it on GitHub https://github.com/Ralim/IronOS/issues/1141#issuecomment-1002468876, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGYNG3K6UCWIXEJNYXFM5LUTLEY5ANCNFSM5KU4LGIQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you modified the open/close state.
Describe the bug The IronOS/Documentation/Flashing.md document suggests following command for flashing a Pinecil:
dfu-util -D Pinecil_EN.dfu
.dfu files were replaced by .bin files in the current stable version. Trying to flash a .bin file with this command does not work because dfu-util finds the option bytes as a separate alt-setting.To Reproduce
Expected behavior The command for flashing a Pinecil should be instead:
dfu-util -d 28e9:0189 -a 0 -D Pinecil_DE.bin -s 0x08000000
the -s option is necessary for raw binary download. Otherwise the following message is displayed:
Details on your device: