arti has quit [Quit: No Ping reply in 180 seconds.]
arti has joined #linux-sunxi
wasutton3 has joined #linux-sunxi
wasutton- has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
bauen1 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
arti_ has joined #linux-sunxi
arti has quit [Ping timeout: 480 seconds]
dsimic is now known as Guest1075
dsimic has joined #linux-sunxi
Guest1075 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
vagrantc has joined #linux-sunxi
ftg has joined #linux-sunxi
warpme has quit []
Parthiban has joined #linux-sunxi
<Parthiban>
Hi All, Am currently trying to flash A133 based custom PCB and found that sunxi-fel is missing the support for this SoC. Is there any other way to flash using Linux? Thanks.
MatrixTravelerbot[m] has quit []
<apritzel>
parthiban: sunxi-fel itself will not help you much, since it cannot really flash any image (except to SPI flash), but in case you need it, here is some branch: https://github.com/apritzel/sunxi-tools/commits/a133-wip/
AntoniAloyTorrens[m]1 has quit []
<Parthiban>
apritzel: Many thanks for sharing that. cherry-pick and tried loading the boot0 image, but the device resets into FEL mode again. `./sunxi-fel spl ../bin/spl/boot0_sdcard_sun50iw10p1.bin`. Am I using the correct file? or should it be fex file?
nashpa has quit []
dliviu has joined #linux-sunxi
<Parthiban>
to add, boot0_sdcard_sun50iw10p1.bin is 60K. Looking at the user manual memory mapping, we have 228K SRAM mapped at A1, C and A2. Hope the size is not the problem, am missing something else.
apritzel has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
<wens>
got a kasan slab-out-of-bounds warning in sun50i_cpufreq_nvmem_probe
<wens>
on H618
ungeskriptet has joined #linux-sunxi
aedancullen has quit []
KREYREN has quit []
cmeerw[m] has quit []
dickenhobelix[m] has quit []
apritzel has joined #linux-sunxi
<apritzel>
parthiban: what do you expect to happen, exactly? sunxi-fel apparently loads boot0.bin correctly into SRAM, then executes it, as requested, but this won't give you much, except initialised DRAM, if you are lucky
<apritzel>
you would need to continue uploading payloads like U-Boot or a kernel. If boot0 worked, then you can do this in DRAM, which is a big win, but just boot0 on its is probably not helpful
<apritzel>
to access the eMMC, you would need have a working U-Boot, which can write images to the eMMC
<apritzel>
or you can run an uploaded Linux kernel, which then can access the eMMC
<apritzel>
but sunxi-fel on its own does not support flashing to eMMC (or SD card, or NAND flash), it just supports accessing SPI flash
ftg has quit [Read error: Connection reset by peer]
ftg has joined #linux-sunxi
rellla has quit []
hentai has quit [Remote host closed the connection]
rellla has joined #linux-sunxi
ftg has quit [Read error: Connection reset by peer]
sunshavi has quit [Ping timeout: 480 seconds]
sunshavi has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
<apritzel>
macromorgan: tokyovigilante: did any of you ever test the new generic AXP SPL U-Boot driver I sent a while ago?
sunshavi_ has joined #linux-sunxi
sunshavi has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
<tokyovigilante>
apritzel: I haven't had a chance yet but will endeavour to do so, and feed back to you and macromorgan about the new u-boot code.
<apritzel>
I just reworked that series, and dropped the original SPL AXP717 driver, in favour of the new generic one. Will send out a new series tomorrow
<apritzel>
also I have a patch to update the DTs from 6.10-rc, which brings the three Anbernic DTs to the U-Boot tree. Patches with defconfigs would be much appreciated ;-)
<apritzel>
macromorgan: at this point we should go with just three separate defconfigs for now, and can later on then look at a unification
KREYREN_oftc has joined #linux-sunxi
<KREYREN_oftc>
Is there a way to get Secure Boot to work on AllWinner A64?
<apritzel>
KREYREN_oftc: not easily or securely. For proper operation you would need to burn the "secure-boot" fuse, and also burn a key hash into the SID, not sure the latter has been done before
<apritzel>
otherwise you can look at what U-Boot offers, but without the SPL loading being secured by the BROM, this leaves quite a gaping hole
<KREYREN_oftc>
So basically if i screw up the chip is hard bricked and can't be unbricked?