13:15 <sphalerite> I have a gru-bob, running the alarm kernel, and want to fiddle with the firmware. However, flashrom says "Processor detection/init failed." when I try to read the firmware using flashrom -p internal -r file

13:35 <sphalerite> what might be wrong here?

15:02 <adjtm_> sphalerit, http://www.loper-os.org/?cat=7

15:03 <adjtm_> first of all, on chromebooks the firmware is read-only, you need to physically disconnect the battery to change to read-write

15:06 <sphalerite> adjtm_: I just want to read it for a start

15:08 <adjtm_> the link I posted is of a blog from someone who has investigated about bob firmware

16:03 <sphalerite> adjtm_: it doesn't seem to mention any specifics about getting flashrom to work

16:03 <sphalerite> besides making write protection removable, which isn't the problem that I'm having

16:15 <vicencb> asciilifeform: I've just read http://www.loper-os.org/?p=2382

16:15 <vicencb> asciilifeform: A bit-by-bit copy of the SPI to SD will not work because they use different format, see:

16:15 <vicencb> asciilifeform: http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.rockchip#l271

16:33 <asciilifeform> vicencb: thanks , but i already did find this earlier

16:34 <asciilifeform> vicencb: ( and you already know that the c101pa in particular simply won't load fw from sd, the vendor specifically built it to power down sd slot until fw is booted )

16:34 <vicencb> I am trying to achieve the same for kevin.

16:34 <vicencb> My approach is to first make coreboot work on the Sapphire board and then port to kevin because the dev-board is way more debuggable.

16:34 <vicencb> So far, when booting coreboot on the dev-board it reports an exception when executing "exception_init_asm"

16:34 <vicencb> https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/firmware-gru-8785.B/src/arch/arm64/transition_asm.S#162

16:34 <vicencb> Does anybody know why?

16:35 <asciilifeform> vicencb: https://freenode.irclog.whitequark.org/linux-rockchip/2018-09-26#23165091 << earlier thread here, possibly of interest

16:35 <asciilifeform> ( re fw read/write )

16:37 <vicencb> asciilifeform: do you know if kevin also has cr50?

16:38 <asciilifeform> afaik c101pa 2017 edition was the 1st box with cr50. but could be wrong.

16:38 <asciilifeform> i do not currently have a kevin ( was it c200 ? )

16:38 <asciilifeform> if it has usbc jack, and it's a chromebook, it probably has one

16:40 <vicencb> asciilifeform: kevin is aka samsung chromebook plus, so, probably yes

16:40 <vicencb> asciilifeform: I still have not used it, but have an external spi flash programmer ready, so, flashing should not be a problem regardless of cr50

16:41 <asciilifeform> vicencb: when i first got the thing, i soldered probes, but then found that you need a 1.8v programmer

16:42 <vicencb> mine is busblaster based, it has a 1.8v capable buffer, already tested it with a 1V8 spare spi flash

16:42 <asciilifeform> nowadays i simply use the built-in flasher in cr50 ( with newest vendor fw, you can 'unlock' and enable spi )

16:42 <asciilifeform> so usable with an unmodified ( other than pulling battery 1ce to enable writes ) unit

16:43 <vicencb> asciilifeform: good to know, thank you. Got to go, can we continue conversation later?

16:43 <asciilifeform> sure

16:44 <asciilifeform> i look in here once a week or so.

17:17 <adjtm_> vicencb, I think that there is no risk of future revisions of samsung chromebook plus having cr50, because 2018 version switched to Intel

18:54 <Svenska> hi. does anybody know the state of rk3126 devices? is it possible to use mainline u-boot/linux on those?