<eigenform[m]>
is the sfdp write granularity what "page size" means, or is that something entirely different
<eigenform[m]>
* the sfdp-reported write
<eigenform[m]>
*oop i guess not, the page size is 256 on this part
<whitequark[m]>
i think it usually should be, actually
<eigenform[m]>
SFDP says its 64-byte, interesting
<eigenform[m]>
program-page works for me though!
<eigenform[m]>
i gave it 256 bytes and it wrote them ¯\_(ツ)_/¯ works for me hah
<whitequark[cis]>
david.rysk: just tried SWD on a PY32F002 target, seems to work OK at 4 MHz with OpenOCD telnet interface only, but I'm getting really weird errors from gdb about malformed packets and such
<whitequark[cis]>
no idea what's up with that
<duskwuff[m]>
which parameter does that show up in specifically?
<duskwuff[m]>
Oh, heh, that field is kind of bogus. It's a single bit which means "at least 64 bytes" if set, there's another parameter later on, which isn't currently decoded, for the actual value
<duskwuff[m]>
According to the datasheet, the actual page size for your flash is indeed 256 bytes
<eigenform[m]>
good to know, thanks for double checking : )
<whitequark[cis]>
js: some flashes just do not have SFDP info
<whitequark[cis]>
use the datasheet to find out how large it is, etc
<js[m]>
hm, reading, I only get 6 bytes and then 0xFF. weirdly, it's consistently the same 6 bytes and then 0xFF, no matter what frequency even.
<js[m]>
I wonder if that might actually be what's on that flash? In which case, I suppose there must be yet another flash to hold the UEFI
<js[m]>
The bytes are cc 28 aa 07 49 0c
<whitequark[cis]>
it might just be empty, yep
<whitequark[cis]>
try reading it with offsets 1, 2, 3, ...
<js[m]>
good idea
<js[m]>
yeah seems to be the actual contenet
<js[m]>
they really used a 512 KiB flash to store 6 bytes.
<js[m]>
but now I'm confused which chip holds the UEFI 😕
<whitequark[cis]>
js[m]: you can't get smaller ones
Wanda[cis] has joined #glasgow
<Wanda[cis]>
6 random-looking bytes
<Wanda[cis]>
MAC address?
<whitequark[cis]>
was about to say that
<whitequark[cis]>
you'd want that to survive firmware wipes
<js[m]>
whitequark[cis]: Catherine: Well, there's a 64 KiB flash just next to it 😉
<js[m]>
Wanda[cis]: Yes, it is, which is why I deleted the message.
<js[m]>
I was stupid to post it here 😉
<js[m]>
the first 3 bytes are the MAC prefix for ASUStek, so I'm quite sure this is a MAC address, given there are rumors this board is made by ASUS
<js[m]>
so it really is an ASUS board where they didn't want to print ASUS
<whitequark[cis]>
it's mirrored on IRC logs anyway
<js[m]>
whitequark[cis]: Crap ☹️
<whitequark[cis]>
deleting messages doesn't do much
<js[m]>
Anyway, I can't find another chip that looks like flash on the board and I really doubt their UEFI fits into 64 KiB.
<whitequark[cis]>
maybe it's supposed to be on a drive or something
<whitequark[cis]>
embedded devices often boot like this, e.g. raspi
<js[m]>
Oh you mean they put an eMMC?
<whitequark[cis]>
something like that
Attie[m] has joined #glasgow
<Attie[m]>
what is this mystery board? are you able to get it running / shell / execute code / etc...? might be a lot easier to figure out from "inside"
<jn>
oh true, the boot flash might just be in the devicetree of that loongson board
norineko has joined #glasgow
<js[m]>
<Attie[m]> "what is this mystery board..." <- Yeah, I can run it. It's an XC-LS3A6M with a Loongson 3A6000
<js[m]>
ideally I wanted to dump flash before using it as no factory image was released
<Attie[m]>
intriguing... have you powered / used it? the AliExpress listing I found suggests SPI flash for BIOS, but isn't that going to be largely / entirely read only (in the "doesn't get written to" sense)
<Attie[m]>
does it actually do anything without other boot media (USB, SATA, NVMe, etc...)
<js[m]>
Yeah it has a UEFI
<js[m]>
in Chinese 😉
<js[m]>
but SPI that would be read-only?!
<Attie[m]>
i don't mean "read only", rather "doesn't get written to"...
<Attie[m]>
which would make your concern about not using it before getting an image irrelevant
<Attie[m]>
i can't find a better image, but this is what you're looking to dump, yes?
<Attie[m]>
(apologies if I'm chiming in after lots of this has been covered already... i've read some of the scrollback, but not all
<Attie[m]>
* not all)
<js[m]>
<Attie[m]> "which would make your concern..." <- Well, if I boot something, at the very least it will create a UEFI boot entry and store that in SPI
<js[m]>
<Attie[m]> "image.png" <- Yeah
<js[m]>
<Attie[m]> "(apologies if I'm chiming in..." <- Oh don't worry! I'm happy for any help, even if that means repeating things 🙂