TheArchive/mayhem-firmware
1
0
Fork 0
mirror of https://github.com/portapack-mayhem/mayhem-firmware.git synced 2024-11-27 12:05:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Edited to add possible wont boot fix and explanations found with @brumi and others

gullradriel 2023-02-12 22:13:31 +01:00
parent 21186296c5
commit eb23f2112a
1 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Won't-boot.md

@ -23,3 +23,16 @@ If you device won't boot and leaves you on a black screen, then you will need to
_**Note:** H2+ usually require you to hold the **UP key** on the first boot to configure them._
_This is valid from nightly version **n_220412** and stable release version: **v1.5.1**_
# H2+ (and H1) not powering up , just black LCD:
(1) disassemble both boards . (your mileage may vary: for an H2+ it is mandatory , because you can not activate DFU with both boards assembled, and in case of H1, no need to disassemble).
(2) pick up your hackrf, connect it to USB, If it's not bricked and you have a green LED, if H2+ flash it with special fw jumbo77 1.43, if H1 use official fw 1.43. If it is bricked (no green LED), you will need to flash these via DFU.
(3) assemble boards , confirm correct power up. At first power up, keep pressing the appropriate button for your unit for more than 2 secs, until getting correct LCD display.
(4) put the device in hackRF mode and flash latest Mayhem firmware.
## Explanation
Firmware starting at version 1.5.4 and onward contain the <a href="https://github.com/eried/portapack-mayhem/pull/662">Pull Request 662</a> that uses the persistent memory to test and store the hardware and LCD config settings . That memory uses the same back up voltage than the Real Time Clock calendar, both needs a healthy cell battery button voltage. Sometimes, in a re flashing process , although we got good battery cell button voltage, the unit seems to be badly initializing those persistent bytes and we got strange black screen. Doing those above steps probably reset the persistent memory. That's just a guess.