<clever>
sphalerite: ground is easy to find, just ohm things out to a ground, when its off
<samueldr>
(I say should be square since it looks square on their design)
<clever>
sphalerite: power is found with a volt meter, and can be ignored
<clever>
tx/rx, connect one to the rx of your usb, and see if you hear any chars
<samueldr>
so ground looks like the one closed to the outside of the board
<samueldr>
and tx/rx labels are "meaningless" as in some OEM will label the pin you plug RX in RX, and some will name it TX
<samueldr>
because of how you plug RX in TX and TX in RX
<sphalerite>
lol
* samueldr
sighs
<clever>
there is a slight risk of damage, if you connect tx and tx together
<samueldr>
eek, 16:36 already :/ have something this evening and need to do things yet
<clever>
but no risk from rx<->rx
<clever>
so just try connecting a random one to your rx, and then see what comes out
<samueldr>
but yeah, since it's u-boot 2014.xx
<samueldr>
I won't be able to help
<samueldr>
I've never looked at u-boot's things in details and relied on something available since ~2016, or 2018 for UEFI
<samueldr>
though I'm thinking there might be value in figuring out those older u-boot with nixos (and including generation boot) as sometimes mainline just isn't available :/
<samueldr>
(going in with the mindset that it's better to use hardware you already have, than to throw it away and buy something better supported)
<sphalerite>
We have serial! :D
<samueldr>
good
<sphalerite>
woo I can talk to the u-boot!
<samueldr>
tohugh the fact that it's that old of a u-boot means I really don't know how to help better with nixos
<samueldr>
the whole sd_image setup right now pretty much assumes use of the generic distro configuration from newer u-boots
<samueldr>
(or iso image with uefi)
<sphalerite>
eh, it's fine, I'll work something out :)
<sphalerite>
having the serial console is already really helpful
<sphalerite>
if you have any idea how to find a kernel image in an SD image that would also be really helpful
zupo has joined #nixos-aarch64
<sphalerite>
I've found dtbs already, but that's it so far
<samueldr>
there's a page off the rockchip wiki that might help
<samueldr>
AFAIK chrome devices still have the same BootROM, but due to the presence of the SPI chip with their bootloader, the boot process diverge really earl
<samueldr>
y
<samueldr>
at least for the 32 bit RK3228 it apparently would go through the usual rockchip stuff if you futzed around
<sphalerite>
hmm
<samueldr>
I'm confused now, hmmm playing with device trees while having partial knowledge and no good resource is fun
<samueldr>
(especially considering apparently no one has documented device tree overlays with the mainline kernel and mainline device trees)
<samueldr>
for the raspberry pi*
<samueldr>
though just now I think I realized how it worked in a broken way before and now doesn't work
<samueldr>
booted using Tianocore + grub, no device tree loaded, means it used the built-in DT (or maybe one from the UEFI build)
<samueldr>
which that one apparently had symbols(?)
<samueldr>
while the mainline one built by nixos maybe doesn't