narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
djrscally has quit [Ping timeout: 264 seconds]
vagrantc has joined #linux-amlogic
luka177 has quit [Ping timeout: 260 seconds]
vagrantc has quit [Quit: leaving]
montjoie has quit [Ping timeout: 252 seconds]
montjoie has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 260 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 256 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 256 seconds]
chewitt has joined #linux-amlogic
<chewitt> f_: I don't have any AXG boards
<chewitt> the Jethome folks should be able to test for you though
<chewitt> Baylibre (and Neil) should also have samples for testing
<chewitt> my understanding is that AXG and G12A are the 'related' board families, not GXL
<chewitt> although looking at https://linux-meson.com/_images/amlogic-socs.png I could be wrong
<f_> chewitt: GXL and AXG have identical register offsets (at least for DDR-related registers, only the base address is different)
<f_> To find GXL DDR register addresses AXG headers left by amlogic were quite helpful
<f_> (I only had to change the bass address)
<chewitt> btw, did you have some code/tooling to extract the timing data from vendor u-boot?
<f_> yes
<f_> I need to fix bugs in it though
<chewitt> I'm poking around with a minix u9-h box and wanted to extract that config
<f_> As said before, needs fixes
<f_> I can fix it for you if you want :)
<f_> (shouldn't be too hard)
<chewitt> I have the vendor u-boot source, but for some reason I'm failing to build clean fips and the existing ones in the tarball aren't working for me
<f_> mm..sure
<chewitt> the board does boot using the Khadas VIM fips, but then things seem to go bad
<f_> chewitt: hmm, which soc generation
<f_> gxl?
<chewitt> GXM
<chewitt> (which is GXL)
<f_> so basically gxl, firmware-wise :)
<f_> acsbaby only supports S905 acs structs, but it shouldn't be hard to support gxl
<f_> I'll do that, one second..
<chewitt> can it also support a /dev/mmcblkX device as input?
rockosov has quit [Ping timeout: 264 seconds]
<f_> chewitt: u-boot.bin input you mean?
<f_> with BL2+FIP?
<chewitt> yes
<f_> Yes, normally.
<f_> Theoretically, I mean.
<f_> but..uhhh else errx(EINVAL, "types other than \"acs\" aren't supported yet");
rockosov has joined #linux-amlogic
<chewitt> the tool I am ultimately seeking is something that I can point at an emmc device (with vendor u-boot) to dump the stuff needed for fip signing
<f_> yeah, would be nice
<chewitt> the important bits seem to be acs.bin and bl301.bin as those are always 'tweaked' for a particular box
<chewitt> the former with timing data for whatever low-bin DDR3 is on the board
<f_> If you just want the binaries you can dd them out.
<chewitt> the later with remote wake stuff
<chewitt> IR remote power on etc.
<chewitt> not NICs
<f_> chewitt: can I have a dump of your BL2+FIP on that box?
<chewitt> how many sectors to dump?
<chewitt> i.e. tell me the dd command to run
<f_> about 4K is enough
<f_> Preferably you can just dump mmcblkXbootX
<f_> with dd if=/dev/mmcblkXbootX of=mmcblkXbootXdump.bin
<chewitt> I'm booting from SD card at the moment with emmc wiped
<chewitt> and I never install to those boot devices
<chewitt> (not sure what those are about really..)
<f_> these boot devices also have BL2+FIP
<f_> But are you booting vendor u-boot from SD?
naoki has joined #linux-amlogic
<chewitt> no, currently experimenting with mainline u-boot
<chewitt> I'm currently tracking down the vendor firmware(s) needed to restore that
<f_> ah
<f_> so I guess this dump is using VIM fip binaries?
naoki has quit [Client Quit]
luka177 has joined #linux-amlogic
<chewitt> correct
<f_> sure
naoki has joined #linux-amlogic
naoki has quit [Client Quit]
<chewitt> sweet .. I finally got the Amlogic card maker tool to work under Win11/Fusion
<chewitt> now I can reflash the box from an SD card
<chewitt> the normal burning tool app never works under Fusion as the macOS side never sees something connected to the USB ports, so never prompts to pass that through to Windows
<f_> haha
<f_> When you're done, can you dump BL2+FIP?
<f_> The box's original ones are the ones I'm interested in.
psydroid has joined #linux-amlogic
<chewitt> first 4MB from /dev/mmcblk1 and the two bootX devices
<f_> thanks
buzzmarshall has joined #linux-amlogic
<f_> FYI: 0000a510: 6163 735f 5f24 0100 4000 0000 0000 0000 acs__$..@.......
<f_> This is the start of the acs struct
anessen9733 has quit [Quit: Ping timeout (120 seconds)]
anessen9733 has joined #linux-amlogic
<f_> chewitt: you just want the binaries right?
<f_> the ACS binary starts at offset 0xa200 and ends at 0xa550
<f_> It's usually expected to be found at 0xd900a000 by gxl BL2 anyway
<f_> so you can just dd that part out
<f_> and add this part at the start: https://paste.debian.net/1310154/
<f_> there's our crafted acs.bin https://0x0.st/HhBv.bin
<f_> chewitt: can you test this ^ acs.bin I just sent?
<chewitt> f_ I'll test in a bit .. watching Rugby at the moment :)
<f_> heh
<chewitt> that file was a complete acs.bin?
<chewitt> if yes, it failed
<f_> mm
<f_> I think something went wrong there
<f_> chewitt: Try this one https://0x0.st/HhMQ.bin
<f_> looks like the footer was somewhere where it shouldn't be.
chewitt has quit [Quit: Zzz..]
luka177 has quit [Ping timeout: 264 seconds]
zsoltiv_ has joined #linux-amlogic
vagrantc has joined #linux-amlogic
naoki has joined #linux-amlogic
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
luka177 has joined #linux-amlogic
naoki has quit [Quit: naoki]
psydroid has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
vagrantc has quit [Quit: leaving]
naoki has joined #linux-amlogic