<smaeul>
there's a lot that could be done to improve the fuzzer tool (nops for random alignment, changing the clock speed, etc.), but it's enough to tell me that I should remove "-msext" from my CFLAGS
<smaeul>
hopefully that will fix things enough that I can go back to working on the actual firmware part
TheSeven has quit [Ping timeout: 240 seconds]
TheSeven has joined #linux-sunxi
shfil has quit [Quit: Connection closed for inactivity]
lurchi__ has joined #linux-sunxi
lurchi_ has quit [Read error: Connection reset by peer]
return0e has quit [Read error: Connection reset by peer]
return0e_ has joined #linux-sunxi
dddddd has quit [Remote host closed the connection]
return0e_ has quit [Ping timeout: 250 seconds]
tl_lim has joined #linux-sunxi
afaerber has joined #linux-sunxi
afaerber has quit [Remote host closed the connection]
vagrantc_ has quit [Quit: leaving]
JohnDoe_71Rus has joined #linux-sunxi
tl_lim has quit [Ping timeout: 268 seconds]
tl_lim has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
f0xx has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 245 seconds]
return0e has joined #linux-sunxi
tl_lim has quit [Ping timeout: 246 seconds]
camus has joined #linux-sunxi
kaspter has quit [Ping timeout: 255 seconds]
camus is now known as kaspter
tl_lim has joined #linux-sunxi
wwilly has quit [Read error: Connection reset by peer]
wwilly has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
sutke11782 has quit [Remote host closed the connection]
sutke11782 has joined #linux-sunxi
wwilly has quit [Ping timeout: 246 seconds]
return0e has quit [Ping timeout: 246 seconds]
tl_lim has quit [Remote host closed the connection]
tl_lim has joined #linux-sunxi
sutke11782 has quit [Remote host closed the connection]
TheSeven has quit [Ping timeout: 250 seconds]
TheSeven has joined #linux-sunxi
Putti has joined #linux-sunxi
netlynx has joined #linux-sunxi
_whitelogger has joined #linux-sunxi
pcbBob has joined #linux-sunxi
pcbBob has quit [Ping timeout: 256 seconds]
pcbBob has joined #linux-sunxi
nuuuciano__ has quit [Ping timeout: 245 seconds]
nuuuciano__ has joined #linux-sunxi
nashpa has quit [Ping timeout: 250 seconds]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-sunxi
KotCzarny has joined #linux-sunxi
wwilly has joined #linux-sunxi
wwilly has quit [Ping timeout: 255 seconds]
_whitelogger has joined #linux-sunxi
dddddd has joined #linux-sunxi
curlybracket has quit [Ping timeout: 255 seconds]
_whitelogger has joined #linux-sunxi
curlybracket has joined #linux-sunxi
clemens3 has joined #linux-sunxi
nashpa has joined #linux-sunxi
clemens3 has quit [Ping timeout: 246 seconds]
nuuuciano__ has quit [Ping timeout: 268 seconds]
AneoX_ has joined #linux-sunxi
AneoX has quit [Ping timeout: 255 seconds]
freemangordon has quit [Remote host closed the connection]
Mangy_Dog has joined #linux-sunxi
return0e has joined #linux-sunxi
wwilly_ has joined #linux-sunxi
wwilly has quit [Read error: Connection reset by peer]
libv_ is now known as libv
Putti has quit [Ping timeout: 255 seconds]
agraf has quit [Read error: Connection reset by peer]
agraf has joined #linux-sunxi
tl_lim has quit [Read error: Connection reset by peer]
shfil has joined #linux-sunxi
wwilly_ has quit [Ping timeout: 250 seconds]
wwilly has joined #linux-sunxi
clemens3 has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
reinforce has joined #linux-sunxi
Rafael1980 has joined #linux-sunxi
\\Mr_C\\ has joined #linux-sunxi
Putti has joined #linux-sunxi
shfil has quit [Quit: Connection closed for inactivity]
tuxd3v has joined #linux-sunxi
<tuxd3v>
Hello All,
<tuxd3v>
Does any one knows if mainline kernel needs to be paired with some special version of uboot?
<mru>
which chip?
<tuxd3v>
H6
<MoeIcenowy>
mainline kernel needs to be paired with mainline U-Boot (and ATF)
<MoeIcenowy>
for 64-bit Allwinner SoCs
AneoX has joined #linux-sunxi
<tuxd3v>
Can I compile it in 64 bits?
AneoX_ has quit [Ping timeout: 245 seconds]
<tuxd3v>
Or I need to have a separated 32 bits toolchain?
<smaeul>
you can compile both ATF and U-Boot with a 64-bit (aarch64) toolchain
<tuxd3v>
So I only need a toolchain?sweet .. :)
<tuxd3v>
The unique requirement is the dts file, or I need to use the fex format?
<MoeIcenowy>
FEX is never used by mainline
<tuxd3v>
Sweet
<tuxd3v>
thanks you all, for the help..
<tuxd3v>
I will try mainline uboot compiled for aarch64
<tuxd3v>
:)
Andy-D has quit [Ping timeout: 255 seconds]
_whitelogger has joined #linux-sunxi
return0e_ has joined #linux-sunxi
return0e has quit [Ping timeout: 245 seconds]
<fALSO>
tuxd3v, it works
<tuxd3v>
FALSO, thanks
<tuxd3v>
I am having a hadr time in choosing a good version of ubbot, because they don't have a release branch
<tuxd3v>
I think
<fALSO>
use master
<fALSO>
it works for my h6, you need to use serial
<fALSO>
apply this patch to the kernel to have ethernet working ;-)
<tuxd3v>
nice
<tuxd3v>
and ethernet is stable?
<fALSO>
it *works*
<fALSO>
i tried for a few days , it worked ok
<fALSO>
this board is yet VERY GREEN
<tuxd3v>
Ok, I had already compiled a kernel for it, but I will patch and compile it
<tuxd3v>
I am with 5.0.4 mainline kernel
<tuxd3v>
bulding with it..
<tuxd3v>
I tried a 4.9 kernel some week ago, at CPU got a lot hot
<tuxd3v>
50 plus C
<tuxd3v>
with a heatsink and a fan above..
<tuxd3v>
:D
<tuxd3v>
I hope for the better now, I revised dts file
shfil has joined #linux-sunxi
<fALSO>
tuxd3v, theres no new changes on the DTS
<fALSO>
so i doubt theres any difference...
<fALSO>
;-)
<fALSO>
no one seems very interested in these boards
<fALSO>
i am still gaining courage to submit that patch :-P
<tuxd3v>
well that CPU is awesome
<tuxd3v>
properly clocked at 1.8Ghz
<tuxd3v>
and it has a lot of power for graphics, and so..
<tuxd3v>
for me the best 4 core A53 around
<tuxd3v>
:)
<tuxd3v>
the PCIe shouldnt have support for what I have read..
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-sunxi
<fALSO>
yes, from what it looks
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #linux-sunxi
<pcbBob>
The F1C600 user manual doesn't really say anything about what the specifications of the SPI flash should be if code is fetched from it after BROM? What would be the minimum size to fit uboot? I never actually compiled uboot so I don't know. I don't plan to run linux after uboot, just my own source code "bare-metal" style
<pcbBob>
So I would say 1Mbyte free space for my source code is way more than I would ever need
<pcbBob>
So 1Mbyte + uboot size
<tuxd3v>
brom is 32k in size
<tuxd3v>
in that faze you can boot from spi flash and so
<pcbBob>
but how big should the SPI flash be to be able to store uboot on it?
<pcbBob>
or any usual uboot, I don't think they differ that much in terms of size
clemens3 has quit [Ping timeout: 245 seconds]
<aalm>
pcbBob, 8mb?
<aalm>
that would fit u-boot, linux kernel, busybox and what not
<pcbBob>
So I assume 4Mbyte are enough for just u-boot? 4Mbyte are available for 0.23$ an aliexpress
<pcbBob>
Still wondering why there are no specifications for the spi flash in the allwinner user manual
<smaeul>
pcbBob: u-boot itself is less that one megabyte
<tuxd3v>
brom checks 1st for sdcard, then emmc, them nand flash, then spi nor
<smaeul>
there's probably no spec because "anything JEDEC" will work
<[TheBug]>
<tuxd3v> the PCIe shouldnt have support for what I have read.. <- Not in Linux but several have said that PCIe will work in a BSD implementation which will likely show up
<tuxd3v>
by that order.
<tuxd3v>
TheBug, interesting to know that
<[TheBug]>
supposedly it handles it by some type or special wrapper that handles it.
<tuxd3v>
becasue it would be amazing to have that
<[TheBug]>
thought I would think the BSD implementation will be without graphics support
<[TheBug]>
though*
bonbons has joined #linux-sunxi
<pcbBob>
tux3dv Sorry to ask again, I am getting confused by this wiki-page: http://linux-sunxi.org/BROM (1. SC Card, 2. Internal Nand flash, 3. SD Card, 4. SPI Nor flash). The reason I am getting confused is that I didn't find any information on the F1C600/F1C100S documents if they have internal nand flash?
<tuxd3v>
it has
<tuxd3v>
for brom
<tuxd3v>
32kb
nashpa has quit [Read error: Connection reset by peer]
nashpa has joined #linux-sunxi
<tuxd3v>
but usually you don't need to worry with it
<tuxd3v>
since it does its job
<tuxd3v>
you can consult Allwinner H6 v200 usermanual
<tuxd3v>
also you can upgrade it, the brom..but I don't advise you too, because if a mistake hapens, you could not be able to bring it to that fase to reflash the Brom
<smaeul>
tuxd3v: no, the BROM is not stored on nand flash
<smaeul>
and you cannot upgrade it
<tuxd3v>
humm, I think it is, since it permits its own upgrade via usb otg
<smaeul>
tuxd3v: the BROM is a mask ROM
<tuxd3v>
its a boot loader
<aalm>
don't think it does
<tuxd3v>
that then boots boot0
<smaeul>
pcbBob: the F1C600/F1C100S doesn't support NAND boot because it doesn't have a NAND controller
<tuxd3v>
So, How to upgrade BROm?
<aalm>
you don't
<tuxd3v>
does it do a jump to a section of the flash?
<aalm>
it's on the chip
<smaeul>
pcbBob: "Internal Nand" on that wiki page means on the PCB, not inside the SoC
<tuxd3v>
You can upgrade it
<smaeul>
tuxd3v: no, you can't, and please stop saying so
<tuxd3v>
its size its 32KB
<smaeul>
you're confusing people
<pcbBob>
So just to go through it step by step: If I have my compiled uboot binary and I want to put it on my SPI Nor Flash (for example sending the bytes through my USB-to-UART converter from a PC to a Microcontroller which then speaks to the flash via SPI) - do I just consecutively write the bytes to the SPI Nor Flash?
<pcbBob>
Or is there something I have to consider so that the F1C100 can execute the code on it?
<tuxd3v>
check section 3.2.1 of v200 user manual
<aalm>
pcbBob, i believe u-boot produces ready2flash binary for you
<smaeul>
pcbBob: you would take the u-boot-sunxi-with-spi.bin (for all of u-boot) or sunxi-spl.bin (for just SPL) and write it byte-by-byte starting at the beginning of the flash
<aalm>
but if you follow the advice from yesterday, you don't have to 'mess' with writing the flash with a mcu, since you can load binary via fel to do the flashing for you
<pcbBob>
tuxd3v do you think this is applicable to a F1C100?
<pcbBob>
aalm I remember you saying it but I am quite afraid to mess with "fel" because I don't even know what that means. But if it's possible it is probably the better way to do so. Just thought a separate microcontroller would be easier to handle
<smaeul>
pcbBob: there's no special offsets, and the header is already created by the u-boot build process
<aalm>
pcbBob, it's a simple commandline tool for interacting w/the brom via usb
<pcbBob>
tux3dv It is an old ARM9 CPU, H6 is too complex for me at the moment
nuuuciano__ has joined #linux-sunxi
<aalm>
actually, i suggest you load the u-boot via that, and then use 'tools' provided by u-boot to do the spi flashing
return0e_ has quit [Read error: Connection reset by peer]
return0e has joined #linux-sunxi
<pcbBob>
aalm but I have to somehow the uboot on that SPI flash to actually boot from it, don't I? I didn't want to use an SD-Card
<pcbBob>
*put
<smaeul>
no, you can use sunxi-fel to copy u-boot over usb into SRAM and run it
<smaeul>
then you copy (another copy of) u-boot to DRAM
<smaeul>
and use the `sf` command in the u-boot shell to write that second copy to SPI flash
<smaeul>
then you unplug the USB, reset, and it boots u-boot from SPI
<aalm>
the first u-boot will initialize DRAM and spi etc. for you
<aalm>
and naturally it won't be there after reset anymore, so like written above, you get the boot from spi
<pcbBob>
The F1C100S for example only has 32kbyte of Instruction Cache, I don't see how uboot would fit into that? Or do you speak mean some tiny uboot version I don't know about?
<pcbBob>
And why (and more important: how) do I copy something to DRAM?
<aalm>
it's in the /BROM
<smaeul>
pcbBob: There's SRAM in the SoC. you're not using Cache-as-RAM
<smaeul>
pcbBob: section 3.1
<smaeul>
SRAM A is 40k
<smaeul>
u-boot spl is 32k
<aalm>
err, the limit is in the /BROM, it doesn't copy whole u-boot, at once, it does load spl first, which is usually <32kb, 24kb for some
<smaeul>
so you load SPL into SRAM A. SPL runs and turns on DRAM
<smaeul>
then SPL returns back to FEL mode and you can load the full u-boot into DRAM
<smaeul>
pcbBob: the sunxi-fel tool automates this whole process
<smaeul>
pcbBob: copying to DRAM is the same as copying to SRAM, it's just a memory address. the caveat is that you have to turn on the DRAM controller first
freemangordon has joined #linux-sunxi
shfil has quit [Quit: Connection closed for inactivity]
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in]
MoeIcenowy has joined #linux-sunxi
<pcbBob>
smaeul & aalm thanks alot for your help guys, I really appreciate it. It doesn't sound too complex in my mind right now
<pcbBob>
I found this document here claiming that F1C100A, F1C100S, F1C500, F1C600 etc. are sharing same die ( https://www.phoronix.com/scan.php?page=news_item&px=Allwinner-SUNIV-ARM9-Kernel ) but they don't mention the F1C100 (just that it's so old it still supports SDR RAM). I am not sure - does the F1C100 fall into the same category, e.g. sharing same die with F1C600 etc? I am asking because it is even cheaper on aliexpress than the F