Notices by Joel Michael (jpm@aus.social)

@whitequark @azonenberg and judging by the photos, the u-blox parts definitely came out of a dumpster because it’s missing the RF shield

@whitequark

UBX-NAV-PVT length = 92 bytes
UBX-NAV-SOL length = 52 bytes
UBX-NAV-SAT length = how many satellites can you see right now?

@whitequark *giggle*

@whitequark I’m pretty familiar with uBlox M8 GPS receivers, feel free to ping if any questions.

My t-shirt is raising a lot of questions answered by my t-shirt #StraightOuttaShenzen

https://www.aliexpress.com/item/1005005766810729.html

@whitequark jumbo frames are real and they can hurt you

@whitequark let me guess, it drives a LED doesn’t it?

@whitequark Oh is that the new 2-wire industrial ethernet stuff?

@whitequark Usually UART because it’s mostly for splatting out shotgun printf() while developing. Don’t have any firmware handy, I’m being Weekend Dad now.

@whitequark yes please, SWO very handy on the MCUs that support it (ie not M0)

@whitequark Also I would like the moon on a stick, or a unicorn.

Seriously though, SWD + UART is a damn good achievement. Now I need to dig up a 1.27mm pitch 2x5 connector breakout. Maybe roll my own that plugs straight into a Glasgow IO bank.

@whitequark Debug probe + UART (that both work reliably, unlike the WCH Link-E) is the dream. Debug probe + UART + bus snoopers would be magical.

@whitequark Oof yeah the LCSC parametric search, where your options are sometimes “-“, “no”, “plugin”, and “yellow/尿”

@whitequark It’s 14-pin so that would narrow the search space a bit? That would probably be a pair of dual-colour LEDs

@whitequark Of you ever make it to .au, or if I make it to .uk again, you’re on (but I owe you at least that for making Amaranth and Glasgow)

@whitequark The biggest hint was it is 96 DQFN, combined with “ethernet” and the first search hit was it. Appears that pin 1 is marked by a dot on the board, and the data lines on the chip appear to be pointed towards the DNP 8P8C socket on the left edge of the board, so that was enough for me to suggest it.

@whitequark Possibly 88E1111?

https://www.marvell.com/content/dam/marvell/en/public-collateral/transceivers/marvell-phys-transceivers-alaska-88e1111-datasheet.pdf

@whitequark you may not like it, but this is the ideal electronics form.

@whitequark lolno, the debug protocol documentation appears to be completely missing for the QingKeV4 CPU. There’s versions floating around for V2, but that’s a different wire protocol. There are references to the debugger manual in the QingKeV4 Processor Manual in the section about debug registers at https://www.wch-ic.com/downloads/QingKeV4_Processor_Manual_PDF.html

@whitequark (unfortunately it’s not standard JTAG - the higher-end parts use something that kinda sorta vaguely resembles ARM SWDIO 2-wire debug, and the low-end parts use a custom 1-wire protocol)