HWFLY stuck on training
- Thread starter Plermpel
- Start date
- Views 13,533
- Replies 25
Same problem. Nand is a SKhynix H26M74002HMR.
Spacecraft 0.7.1 is on my HWFLY v4.
Putty Diagnose status: BAD00124
Found the solution:
The flex cable was not soldered correctly. The top of the A didn't connect to the bottom (the HWFLY chip). I did not tin the pins of the HWFLY chip before soldering the flex cable. So everything looked fine but the error was hiding underneath.
Spacecraft 0.7.1 is on my HWFLY v4.
Putty Diagnose status: BAD00124
Code:
> d
# Diagnosing...
# Diagnose report:
Device type: unknown
Done.
# Diagnose status: BAD00107
# Please make sure console is powered on
> d
# Diagnosing...
# Diagnose rep ort:
Device type: Lite
adc: 1007 (flag 3000)
adc: 1003 (flag 0)
adc: 998 (flag 0)
adc : 1000 (flag 0)
adc: 1315 (flag 1000)
# Status: BAD00110
Done.
# Diagnose status: BAD00110
> d
# Diagnosing...
# Diagnose report:
Device type: Lite
adc: 1318 (flag 3000)
adc: 1315 (flag 1000)
Glitching started
glitch info : [840, 50, 0] {0} 44 60
glitch info: [840, 50, 1] {0} 44 60
glitch info: [840, 50, 2] {0} 44 60
glitch info: [840, 50, 3] {0} 44 60
glitch info: [840, 50, 0] {0} 44 60
glitch info: [840, 50, 1] {0} 44 60
gli tch info: [840, 50, 2] {0} 44 60
glitch info: [840, 50, 3] {0} 44 60
Done.
# Diagnose status: BAD00124
> d
# Diagnosing...
# Diagnose report:
Device type: Lite
adc: 1006 (flag 3000)
adc: 1007 (flag 0)
adc: 1000 (flag 0)
adc: 999 (flag 0)
adc: 1314 (flag 1000)
Glitching started
glitch info: [840, 50, 0] {0} 44 60
glitch info : [840, 50, 1] {0} 44 60
glitch info: [840, 50, 2] {0} 44 60
glitch info: [840, 50, 3] {0} 44 60
glitch info: [840, 50, 0] {0} 44 60
glitch info: [840, 50, 1] {0} 44 60
glitch info: [840, 50, 2] {0} 44 60
gli tch info: [840, 50, 3] {0} 44 60
Done.
# Diagnose status: BAD00124The flex cable was not soldered correctly. The top of the A didn't connect to the bottom (the HWFLY chip). I did not tin the pins of the HWFLY chip before soldering the flex cable. So everything looked fine but the error was hiding underneath.
Attachments
Last edited by Moneyforthecash,
I recently came across this issue after ordering a hwfly V4 oled and noticed when disconnecting the cpu ribbon the chip wouldn't even power on, which led me to checking the 3v3 and gnd, and low and behold the ribbon I was supplied had no actual ground connection 
wired it up manually and it worked... Gotta love QC
wired it up manually and it worked... Gotta love QC
Afaik it's designed like that. All ground pads on the QSB ribbon are for anchoring and are not connected anywhere. If you refer to their own installation diagrams, ground pad on the chip isn't even soldered as they use sp1/sp2 on cpu cable for ground.I recently came across this issue after ordering a hwfly V4 oled and noticed when disconnecting the cpu ribbon the chip wouldn't even power on, which led me to checking the 3v3 and gnd, and low and behold the ribbon I was supplied had no actual ground connection
Btw I never use that qsb ribbon cable since it puts stress on A and D points. Just use jumper wires and imo it's even easier to solder and troubleshoot. For ground I usually solder to the other end of the 3.3v capacitor.
Hello, glad that you fixed your problem. I have the same issue. I saw that you have mentioned earlier that you double checked all the connections and they are all in range, according to sthetix tutorial. In this case, you still had a problem with point D? Can you explain more about the problem you had with point D and how did you fix it? thank you!
Similar threads
