04:12 <chewitt> Tartarus: most Amlogic boards support direct flashing of an image to emmc via the Amlogic "USB Burning Tool"

04:12 <chewitt> it's a windows app and you connect the board via one of the USB ports

04:13 <chewitt> the image needs to be in the right format, it's not any old .img file

04:14 <chewitt> and in your case you don't need to be picky about the ROM file that's restored

04:15 <chewitt> as long as you end up with u-boot that will boot (at least as far as the u-boot console) .. you can do more things

06:28 <repk> Tartarus: There are some report of usable pin to short. So I would probe on pins/cap/etc nearby the eMMC or under it to find something that looks like a CLK or Data and short that to ground. Maybe you would find yourself lucky

06:50 <narmstrong> Tartarus: in this case either you find the test point to short, otherwise you build yourself this dongle https://github.com/superna9999/linux/wiki/Amlogic-HDMI-Boot-Dongle

06:51 <narmstrong> Tartarus: you can try to short each test point close or underneath the emmc

07:10 <repk> haha nice dongle

07:27 <narmstrong> repk: did you have time to look at my PCIe patches ?

07:28 <repk> narmstrong: yes I did, is it worth that I reply with a review by ?

07:34 <narmstrong> repk: as you want, maybe patch 2 concerning the clock renames

07:37 <warpme_> guys: just quick update regarding plays with s3 suspend & vrtc on s905 (tx3 mini): I applied patches; rtc is loading but i’m not able to test as i simply can’t soft power-off system. it just reboots. i can suspend but there is no way to resume. if you have any pointers - i’ll be greatful

07:38 <narmstrong> warpme_: use `rtcwake -s 10 -m mem`, ti will program the rtc to wake you un 10seconds

07:45 <warpme_> narmstrong: thx. it looks first i need to cross-build rtcwake tool :-p. i’ll let you know about results....

11:20 <Tartarus> repk, narmstrong, OK, thanks. I'll take a look harder if I manage to brick the second of these boards.

11:20 <Tartarus> narmstrong: Do you use something like that HDMI dongle for U-Boot work then so you can force SD boot?

11:23 <repk> Tartarus: If I am not wrong, you can just write invalid data in the eMMC (e.g. set first byte to 0) the CPU will fallback into SD boot.

11:26 <narmstrong> Tartarus: yes

11:27 <narmstrong> repk: but you must boot before ;-)

11:28 <Tartarus> Ah fun :)

11:28 <Tartarus> narmstrong: Any chance you know if the BCB stuff in mainline is good / complete enough to stand in for the "normal" amlogic vendor flash method?

12:35 <warpme_> narmstrong: just FYI regarding rtc wakeup on s905: issuing ‚rtcwake -d /dev/rtc0 -s 20 -m mem’ simply hangs my system. all looks like freezed (including screen).

12:38 <narmstrong> Tartarus: we haven't integrated BCB yet, but it looks complete enough to get the reboot reason

12:38 <narmstrong> Tartarus: but I don't see what you mean by stand in for the "normal" amlogic vendor flash method, you want to boot the amlogic android release over mainline u-boot ?

12:39 <Tartarus> narmstrong: Thinking out loud a little.

12:40 <Tartarus> Not that I can push amlogic in that direction but what would it take for mainline to do everything the vendor fork(s) do

12:46 <narmstrong> We are working on it, essemtially the vendor has a lot of security features handled, and it's easier to handle them in an (old) fork

12:47 <narmstrong> AVB will be touchy since they implemented AVB helpers in the BL2, but simpler than loading a TA for sure