Headphone Failure about portapack-havoc HOT 7 CLOSED

@eried Yep, think that's what I am going to do. Seller offered to exchange, but that will be weeks of down time. Now its just become a puzzle I must solve, so digging deep into circuit a rewarding experience.

from portapack-havoc.

Do you have another portapack to test? The clones are quite cheap in aliexpress and a backup wont harm.

BTW, I dont think this issue is really related to havoc

from portapack-havoc.

@SannhetJaeger I suspect your portapack to be a chines clone. Can you confirm that yours looks exactly like the one on the sharebrained website ? (especially the silkscreen) https://sharebrained.com/

Furthermore, furrtek/portapack-havoc is a repository related to firmware development. So don't expect many interesting replies related to an hardware issue. See peppa pig's advises in README.md

Best bet is to ask to the seller. To reassure, you are pretty safe if you bought your portapack from sharebrained or a re-seller.

from portapack-havoc.

Yup, seller selling crap -> seller's problem.
The firmware does have a ton of bugs but something as basic as audio output and touchscreen support must work.

from portapack-havoc.

Indeed, it's produced in China. For a hobby item, it fit the budget. Do appreciate the feedback though. Engineering wise, it matches exactly to KiCad schematics / footprint. Under microscope, it's quite clean. Didn't have enough jumpers to flip board over to test with logic analyzer - waiting of snail mail to deliver more. Since all other functions work and the radio is well calibrated per scope, this will just be a pet project to learn on. If it can be built, it can be fixed :-).

In the meanwhile, I am figuring out how to get some insights into the init sequence. I'll look through the code to see about re-enabling the debug screen (saw another person asking about this) as an option from settings, with perhaps some test functions with captured register states; maybe these test routines are in older versions of firmware. Not sure if there are ways to do this interactively from CLI when in hackrf mode?

(I'll mark this as closed since its clearly hardware issue - if anyone has ideas on debug, would appreciate links / pointers - thanks - cheers)

from portapack-havoc.

FYI - turns out idiots that manufactured board put the AK4951 chip on board 90 degrees rotated. Think that might cause issues? Rotated chip and its working as expected... Lesson #90 +/- 2M, check for chip pin 1 placement early in troubleshooting - way before reflowing and logic analyzing board...

from portapack-havoc.

Wow that's some great QA...

from portapack-havoc.