ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
<machinehum> I've been using a uboot patch with buildroot and using the sdcard.img, but I'll start flashing the u-boot-sunxi-with-spl.bin directly
vagrantc has quit [Quit: leaving]
<apritzel> yeah, I'd prefer removing all those middle men, too many things that could go wrong, especially with a new SoC
<apritzel> machinehum: get https://paste.c-net.org/ShavedDumber, and write that to the SD card (as above)
<machinehum> dd it?
<machinehum> Or copy the file
<machinehum> Also
<machinehum> What about all the AXP805 stuff?
<machinehum> Should that not all be enabled in uboot, set the regulator voltages, etc...?
<apritzel> machinehum: you should try walking before you run ;-)
<apritzel> machinehum: dd if=uart_init_v5.sunxi of=/dev/sdX bs=1k seek=8
<apritzel> (where /dev/sdX is the name of your SD card block device)
<apritzel> for now we just need the SPL to print the banner, there is no AXP needed at this point
<machinehum> apritzel: GOtcha
<apritzel> and the DRAM controller might be the biggest hurdle anyway
<machinehum> HELLLOOOO!
<machinehum> That's exciting
<apritzel> very good! This also puts the board in FEL mode (in case there is no FEL button)
<machinehum> Do you have a diff for that? What is going on here
<apritzel> machinehum: this is just some pure assembly to initialise the UART according to the V5 manual and output something, wrapped in an eGON image
<apritzel> it just proves that the UART works with those parameters
<apritzel> try to write spl/sunxi-spl.bin in the same way, with your branch or my patch plus the proper UART pinmux setup, and see if that works
apritzel has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
<machinehum> No dice on that
<machinehum> OH
<machinehum> Does SUNXI_DRAM_DW need to be enabled?
<machinehum> Nevermind
<machinehum> SUNXI_DRAM_CTL0_BASE Seems to be different between the H6 and V5
vagrantc has quit [Quit: leaving]
<jernej> DRAM is initialized after UART, so you should worry about that after you get something printed on UART
JohnDoe_71Rus has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
paulk-bis has quit [Ping timeout: 480 seconds]
evgeny_boger has joined #linux-sunxi
paulk-bis has joined #linux-sunxi
Daanct12 has joined #linux-sunxi
tnovotny has joined #linux-sunxi
veremitz has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
tnovotny has quit [Quit: Leaving]
paulk-bis has quit []
paulk has joined #linux-sunxi
apritzel has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
paulk has quit [Ping timeout: 480 seconds]
adjtm has quit [Quit: Leaving]
Daanct12 has quit [Remote host closed the connection]
paulk has joined #linux-sunxi
cnxsoft1 has joined #linux-sunxi
cnxsoft1 has quit []
cp-- has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 480 seconds]
cp- has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
<MoeIcenowy> machinehum: are you trying to mainline V5 u-boot?
JohnDoe_71Rus has joined #linux-sunxi
pmp-p_ has joined #linux-sunxi
pmp-p has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
adjtm has joined #linux-sunxi
<apritzel> MoeIcenowy: yes, he does, but it doesn't work yet, so mainlining comes much later, I guess
<apritzel> MoeIcenowy: do you have patches lying around, by any chance?
paulk has quit [Ping timeout: 480 seconds]
pmp-p_ has left #linux-sunxi [#linux-sunxi]
paulk has joined #linux-sunxi
pmp-p has joined #linux-sunxi
apritzel_ has joined #linux-sunxi
<machinehum> MoeIcenowy: Yes
<machinehum> Been trying for the past 2 weeks or so
<machinehum> jernej: Alright
<machinehum> MoeIcenowy: RE patches, that would be relly helpful
apritzel has quit [Ping timeout: 480 seconds]
apritzel_ has quit [Ping timeout: 480 seconds]
mps has joined #linux-sunxi
JohnDoe_71Rus has quit []
apritzel_ has joined #linux-sunxi
apritzel_ has left #linux-sunxi [#linux-sunxi]
apritzel has joined #linux-sunxi
vpeter has quit [Remote host closed the connection]
vpeter has joined #linux-sunxi
machinehum has quit [Ping timeout: 480 seconds]
pentabarf1 has joined #linux-sunxi
machinehum has joined #linux-sunxi
megi has quit [Ping timeout: 480 seconds]
megi has joined #linux-sunxi
<pentabarf1> Hi, one year ago @smaeul gave me a hint how to verify the rotpk by using a challenge-response mechanism in the SID. I didn't get it to work then. Now i am trying again. smaeul said "write the ROTPK to SID+0x120...SID+0x140, then set bit 31 of SID+0x140. wait 256 cycles and check SID+0x140 again. I believe bit 1 set means ROTPK is nonzero, and bit 0 means it matches what you wrote". He also said it is for H616 NBROM and i am
<pentabarf1> his is my code so far: https://gist.github.com/pentabarf/8695459ce25b289ae068fd6091502c9c But it is not working right now. What am i missing?
pentabarf1 has quit [Quit: Leaving.]
sunshavi_ has joined #linux-sunxi
<apritzel> pentabarf1: does this actually work from the non-secure side, in Linux?
vagrantc has quit [Quit: leaving]