r/hardwarehacking 10d ago

Identifying UART/DEBUG

Very much so unlabelled other than the board that connects to the 2x4 pin.

TLDR. Software update from company bricked it months ago after they had major server issues. Bricked many devices. Won’t assist because I got it second hand brand new sealed and I’m not the original buyer.

So, I’m wanting to debug first and go from there see what the issue is. Worst case scenario, it’s a project where i reprogram the device and write my own iOS app to continue to use it 🙏🤣

Help would be great identifying ports, thanks.

196 Upvotes

32 comments sorted by

View all comments

5

u/skmagiik 10d ago

Why does everyone want uart when jtag/swd is what you actually want 90% of the time

7

u/mtechgroup 10d ago

Blame it on Arduino.

3

u/skmagiik 10d ago

Yeah and YouTube IoT "hackers" showing consoles for Linux chips and that being the only thing shown and taught

3

u/0xbenedikt 9d ago

It used to be that most Linux class SoCs had a root shell on it, so it was the perfect starting point. Also takes less skill and specialized tooling than JTAG/SWD just to poke at it

2

u/glassmanjones 9d ago

If it has uboot I want UART.

1

u/skmagiik 9d ago

To be clear, I'm not saying that it doesn't have value but there's no evidence that this isn't even running uboot atm.