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
sunshavi_ has quit [Remote host closed the connection]
<anarsoul> MoeIcenowy: ^^
sunshavi_ has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
dikiy has quit [Ping timeout: 480 seconds]
jelly has quit [Ping timeout: 480 seconds]
jelly has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
macromorgan is now known as Guest1182
Guest1182 has quit [Read error: Connection reset by peer]
macromorgan has joined #linux-sunxi
grming has quit [Quit: Konversation terminated!]
Daanct12 has joined #linux-sunxi
Daanct12 has quit [Remote host closed the connection]
<MoeIcenowy> apritzel: I am not sure, but what I heard is A100 is different from A133
<wens> jernej: looks like gstreamer works as well
junari__ has joined #linux-sunxi
junari__ has left #linux-sunxi [#linux-sunxi]
junari__ has joined #linux-sunxi
junari__ has quit [Remote host closed the connection]
junari has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
junari_ is now known as junari
<junari> So, I added to the beginning of board_init_f function (https://source.denx.de/u-boot/u-boot/-/blob/master/arch/arm/mach-sunxi/board.c#L439 ) the reset_cpu() function. As a result, the device with the H616 processor is rebooted, and the device with the T507 is not. Same with sd card.
<junari> Is there anything else before board_init_f() that could affect the load?
<junari> As I understand it, previously there was only a general code for the arm64 platform
JohnDoe_71Rus has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
junari__ has joined #linux-sunxi
junari_ has quit [Read error: No route to host]
junari_ has joined #linux-sunxi
junari_ is now known as junari
junari__ has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
evgeny_boger1 has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
vagrantc has quit [Quit: leaving]
evgeny_boger1 has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
macromorgan has quit [Read error: Connection reset by peer]
apritzel has quit [Ping timeout: 480 seconds]
dikiy has joined #linux-sunxi
<wens> jernej: compared to hantro, running fluster gstreamer test on cedrus additionally fails vp80-00-comprehensive-006 and vp80-00-comprehensive-014. these two are the odd dimension test vectors
evgeny_boger has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
junari__ has joined #linux-sunxi
apritzel has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
<apritzel> junari__: are you sure your code gets actually loaded?
<apritzel> junari__: at least the FEL problems you reported the other day suggested otherwise
junari_ has joined #linux-sunxi
<apritzel> junari__: if you want to debug early code, I'd recommend you use "sunxi-fel spl uart0-helloworld-sdboot.sunxi", before you do the actual load: that sets up the UART.
junari_ is now known as junari
<junari> apritzel: It is hard to say. The problem with 21KB also appears on the H616, but the SPL boot works fine on it
<apritzel> Then you can just do "writel('1', 0x05000000);" or the assembly equivalence
junari__ has quit [Ping timeout: 480 seconds]
<apritzel> junari: yeah, sorry, I still owe you that test with the 21K payload
<junari> I tried putting it at the beginning of the function board_init_f(), but it didn't work
<junari> On t507 and H616 too
<junari> apritzel: sorry, works on H616, don't work on t507
<junari> apritzel: When I start uploading via FEL I get the output on t507: Stack pointers: sp_irq=0x00021400, sp=0x00053FD4 / MMU is not enabled by BROM / => Executing the SPL... done. /usb_bulk_send() ERROR -9: Pipe error
<junari> Now I found, that sp register is different with H616 (sp=0x00053FE4). Could it matter?
<apritzel> junari: not really if it's just 16 bytes
<apritzel> junari: my gut feeling is sunxi-fel does something wrong already with the H616, and we *mostly* get away with it. Apparently the T507 is a bit more picky here.
<apritzel> junari: can you please dump the BROM and put that somewhere? "sunxi-fel read 0 65536 t507_brom.bin"
<junari> Yes, of course
<MoeIcenowy> apritzel: is it possible that the T507 device is secure booted?
<apritzel> MoeIcenowy: I doubt it, and we would see a message from sunxi-fel about doing the smc
<MoeIcenowy> apritzel: do we have secure detection for H616?
<apritzel> ah, good point ...
<apritzel> (as we don't have the secure SRAM A2 to check)
<apritzel> MoeIcenowy: thanks for the answer on the A100, btw. I will then not pretend they are identical, but just closely related
junari_ has joined #linux-sunxi
junari has quit [Read error: Connection reset by peer]
junari_ is now known as junari
<apritzel> junari: thanks
<apritzel> but bummer: seems to be identical to the H616 NBROM
<apritzel> junari: can you check whether "sunxi-fel -v sid" works?
<junari> apritzel: SID key (e-fuses) at 0x03006200
<junari> 33007c00:7c004808:01464701:64841f0e
<apritzel> that seems fine, I don't think this would work when the device is secure fused
<junari> It should have been easy to bring up the T507 with well known H616...
<junari> But it turned out not to be as easy as I expected.
<apritzel> junari: yeah, that's interesting. You could compare the two manuals, especially around the clocks (mostly the PLLs and bus blocks), and the system config
<junari> I'll try to do it again. But it looks like copypaste
evgeny_boger1 has joined #linux-sunxi
warpme____ has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
<apritzel> libv: mnemoc: any chance you can revive the Wiki (that's dead for days now)? Or just switch over to the new version?
<junari> apritzel: yeah, success
<junari> Over RVBARADDR register
bauen1 has quit [Ping timeout: 480 seconds]
<junari> apritzel: thank you for your help
junari_ has joined #linux-sunxi
freemangordon has quit [Ping timeout: 480 seconds]
junari has quit [Read error: No route to host]
junari__ has joined #linux-sunxi
freemangordon has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
freemangordon has quit [Ping timeout: 480 seconds]
freemangordon has joined #linux-sunxi
<apritzel> junari__: good find, though I think we don't use those registers in U-Boot
dikiy has quit [Read error: Connection reset by peer]
freemangordon1 has joined #linux-sunxi
freemangordon has quit [Read error: Connection reset by peer]
junari__ is now known as junari
<apritzel> junari: oh, I see, the base address is different now! I checked that RVBAR was still at +0x40, but didn't check the base ...
<apritzel> but sunxi-fel identifies the SoC as H616, right?
freemangordon has joined #linux-sunxi
freemangordon1 has quit [Read error: Connection reset by peer]
junari_ has joined #linux-sunxi
<apritzel> junari: did you find any BSP code for the T507 out there? Something were we can find something to differentiate between the two? Like we do for the H2+ and H3, for instance
<apritzel> I would guess we can compare SID keys (we have yours already), but it would be good to have something definitive
JohnDoe_71Rus has quit []
junari has quit [Read error: No route to host]
grming has joined #linux-sunxi
junari__ has joined #linux-sunxi
junari__ is now known as junari
evgeny_boger1 has quit [Ping timeout: 480 seconds]
<junari> apritzel: yes, sunxi-fel think that it H616
junari__ has joined #linux-sunxi
junari is now known as Guest1236
junari__ is now known as junari
<junari> sorry, don't understand what you mean about BSP
<apritzel> junari: for the records: this is what we do already to discern closely related SoCs that share a SoC ID: https://github.com/linux-sunxi/sunxi-tools/blob/master/uart0-helloworld-sdboot.c#L319-L353
<apritzel> junari: I meant some Allwinner provided code that shows how to tell T507 apart from H616 (since they have the same SoC ID)
<apritzel> typically that's in their U-Boot, IIUC
junari_ has quit [Ping timeout: 480 seconds]
<junari> Ah, yes, I have some sources for t507
<apritzel> junari: I guess the quickest way would be to check for anything SID related
<apritzel> or search for "H616"
Guest1236 has quit [Ping timeout: 480 seconds]
<apritzel> junari: so to confirm this: if you hack the right RVBAR base address into boot0.h, does it boot?
<junari> apritzel: yes, I can see uart output
<junari> apritzel: here switch for different cpus from u-boot
dikiy has joined #linux-sunxi
<junari> Earlier I posted a link to the source code by MYiR
<apritzel> junari: ah yes, that's the one. Interestingly it puts your SoC as "H503"
<MoeIcenowy> apritzel: A100 is a redacted down-binned version for A133 because of quirks, as I heard
<MoeIcenowy> BTW at least 3 people now ask me how is linux-sunxi.org, when will minima get promoted?
<apritzel> MoeIcenowy: I know, I poked libv and mnemoc already above ;-)
<junari> Over sources and docs for helperbox T507 can be found here http://szbaijie.f3322.net:8088/helperbox/
<junari> Myir sources for T507 http://down.myir-tech.com/MYD-YT507H/
<MoeIcenowy> apritzel: my two sentences are not related at all
<apritzel> MoeIcenowy: I got that ;-)
<apritzel> I wanted to add something to the A133 page, so for me it's related ;-)
<MoeIcenowy> A100 is now discontinued because all new dies meet the criteria for A133
<MoeIcenowy> well this reminded me of F133-A and F133-B
<apritzel> MoeIcenowy: I see, that makes sense
<MoeIcenowy> the former has broken TVIN
evgeny_boger has joined #linux-sunxi
bauen1 has joined #linux-sunxi
freemangordon1 has joined #linux-sunxi
freemangordon has quit [Remote host closed the connection]
freemangordon has joined #linux-sunxi
freemangordon has quit []
freemangordon has joined #linux-sunxi
freemangordon1 has quit [Ping timeout: 480 seconds]
freemangordon has quit []
evgeny_boger has quit [Ping timeout: 480 seconds]
dikiy has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
<mnemoc> apritzel: maxima is still the official wiki, I'll try to get that old *censored* up again. both disks are dying
<apritzel> mnemoc: many thanks, much appreciated!
<mnemoc> pretty upsetting considering Hetzner is charging 70EUR/month for that piece of junk
<mnemoc> hopefully this will be maxima's last month
<mnemoc> up
<apritzel> mnemoc: many thanks, it's indeed working again!
<mnemoc> be gentle please :)
<apritzel> I will try to only change one character at a time ;-)
<mnemoc> :D
junari has quit [Ping timeout: 480 seconds]
<smaeul> apritzel: at some point the SID started allowing the first 0x40 bytes to be read even in NS mode. I don't remember exactly what SoC that started with.
<MoeIcenowy> smaeul: oops
<smaeul> this is so you could still read the SID -- all the key material was moved to the secure-only half
dikiy has joined #linux-sunxi
freemangordon has joined #linux-sunxi
<MoeIcenowy> smaeul: then on H616 where could we use to identify whether we're secure or non-secure?
dliviu has quit [Ping timeout: 480 seconds]
dikiy has quit [Ping timeout: 480 seconds]
<apritzel> we could just try the second half then, given that this is something non-zero in there
ftg has joined #linux-sunxi
<jernej> junari: do you have issues with DRAM initialization?
dikiy has joined #linux-sunxi
vagrantc has joined #linux-sunxi
<jernej> wens: I just tested samples you mentioned with ffmpeg. Each frame md5 matches with reference md5 hash for both samples. I'm certain that Cedrus was used because debug log printed usual messages when using request api.
<jernej> so imo issue is in gstreamer then
jelly has quit []
jelly has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
dliviu has joined #linux-sunxi
gsz has joined #linux-sunxi
JohnDoe_71Rus has quit []
macromorgan has joined #linux-sunxi
apritzel has joined #linux-sunxi
dikiy has quit [Ping timeout: 480 seconds]
rajkosto has joined #linux-sunxi
gsz has quit [Quit: leaving]
bauen1 has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
rajkosto has quit [Quit: Leaving]
apritzel has joined #linux-sunxi
bauen1 has joined #linux-sunxi
warpme____ has quit []
grming has quit [Quit: Konversation terminated!]