01:03 <sjg1> hanetzer: What is the address?

01:03 <sjg1> mps: Seems to work for me:

01:03 <sjg1> https://www.irccloud.com/pastebin/5FsvCHru/

01:04 <hanetzer> sjg1: 0xffff0000 and 0xfffd0000

01:04 <hanetzer> y'kno, where the trm says the bootrom is

01:05 <sjg1> https://www.irccloud.com/pastebin/cKpyAOuN/

01:05 <hanetzer> izzat the arm64 one?

01:05 <hanetzer> since that does not appear to be uh aarch32 code

01:14 <hanetzer> sjg1: do you have uh, network support on that?

01:58 <sjg1> hanetzer: yes, kevin. Yes I can connect USB network

01:59 <hanetzer> I'm not sure exactly what the command formulation would be, but think you could tftp 20k of data from that location out of it?

02:01 <hanetzer> sjg1: ^

02:10 <sjg1> https://www.irccloud.com/pastebin/k0vuA6Cc/

02:10 <sjg1> hanetzer: ^

02:10 <hanetzer> heh

02:11 <sjg1> hanetzer: https://drive.google.com/file/d/1vu8EVyAEXusC4G2Qf8etSDnk6m-Wc-UZ/view?usp=sharing

02:12 <hanetzer> how did ya get that one out, if the first one crashed?

02:13 <sjg1> hanetzer: I suppose it crashed after sending some blocks

02:13 <hanetzer> ah

07:17 <mps> sjg1: I see. do you boot from flash chip or from mmc kernel partition

07:58 <hanetzer> so, as a general rule. if a soc can boot off of the 'user' partition of an mmc, does this also hold true for the bootN parts? or is that something I'm just going to have to try and see, barring the potential of extracting the bootrom and disassembling it?

12:34 <hanetzer> well, good to know: it *does* begin executing code from the eMMC's boot0 partition. bad news: the vendor-boot does not work with it. however we're otherwise good :)

13:10 <sjg1> mps: It boots from SPI flash

13:15 <mps> sjg1: aha, that is difference. I'm trying to boot from mmc

13:16 <mps> so it means I have to find proper method to create image to 'dd' to mmc boot (kernel) partition

13:17 <mps> here is my APKBUILD for alpine (similar to PKGBUILD on Arch linux) https://tpaste.us/lVk6

13:17 <mps> i.e. how I use mkimage and vbutil_kernel

13:18 <mps> maybe there is problem

13:49 <hanetzer> I never got chainloading to work that way tbh.

13:53 <mps> hanetzer: I got it booting fine with alpernebbis u-boot few months ago (in mart or april iirc)

13:54 <hanetzer> did you upgrade the coreboot itself?

13:54 <mps> but I erased mmc and now can't repeat

13:54 <mps> hanetzer: no

16:42 <Forty-Bot> hanetzer: depends on the commands issued by the boot rom; you can set the boot0/boot1 partitions to be the "default" partition

16:42 <Forty-Bot> but if the boot rom issues a command to set the partition explicitly it doesn't matter

16:43 <Forty-Bot> but grats on discovering that

21:57 <marex> hanetzer: I am totally fascinated/impressed by your persistence with this hw :)

22:10 <hanetzer> marex: heh. well. I personally wish I never once looked into a hisi firmware image or at a datasheet XD

22:24 <marex> hanetzer: look at the bright side, there is a datasheet ;-/

22:35 <hanetzer> yeh.