smaeul has quit [Remote host closed the connection]
smaeul has joined #linux-sunxi
tllim has quit [Read error: Connection reset by peer]
smaeul has quit [Quit: cya]
LargePrime has quit [Ping timeout: 265 seconds]
smaeul has joined #linux-sunxi
dddddd has quit [Read error: Connection reset by peer]
anarsoul|2 has quit [Ping timeout: 255 seconds]
lurchi__ is now known as lurchi_
hanetzer has quit [Remote host closed the connection]
hanetzer has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
TheSeven has quit [Disconnected by services]
[7] has joined #linux-sunxi
<anarsoul>
I'm trying to get DVFS working on A64 with embed-3d ths patches
<anarsoul>
so far ths seems to be working - at least it reports reasonable temp, and so does basic cpufreq. But if I add cooling-maps to thermal-zones board powers off very early at kernel startup
<anarsoul>
any idea why?
lkcl has joined #linux-sunxi
nuuuciano has joined #linux-sunxi
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-sunxi
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-sunxi
<anarsoul>
embed-3d: ping :)
victhor has quit [Remote host closed the connection]
nuuuciano has quit [Ping timeout: 248 seconds]
nuuuciano has joined #linux-sunxi
<anarsoul>
commented out orderly_poweroff in thermal_core.c, now I see that it prints "[ 1.939718] thermal thermal_zone0: critical temperature reached (190 C), shutting down"
<anarsoul>
however when it's booted /sys/class/thermal/thermal_zone0/temp reports ~60.1 C
<anarsoul>
so I guess it's a bug in the driver?
hardfalcon has joined #linux-sunxi
<smaeul>
anarsoul: because on a64 the temperature slope is negative, and the initial raw value read from the hardware is 0
<smaeul>
on earlier hardware this was a super low temp and nobody cared, but on a64/h5 it's super high and causes shutdown
<anarsoul>
I see
<smaeul>
it's a known issue for a while; I tried at one time to ignore reads of zero, but the driver was too dense for me to figure it out
<anarsoul>
cool, works just fine - once temp reaches 75c cpu frequency goes down
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
xyntrix has quit [Ping timeout: 264 seconds]
fkluknav has joined #linux-sunxi
[7] has quit [Ping timeout: 255 seconds]
TheSeven has joined #linux-sunxi
lurchi__ has joined #linux-sunxi
TheSeven has quit [Ping timeout: 265 seconds]
lurchi_ has quit [Ping timeout: 255 seconds]
TheSeven has joined #linux-sunxi
Putti has joined #linux-sunxi
fredl-pc has joined #linux-sunxi
Putti has quit [Ping timeout: 255 seconds]
fredl-pc has quit [Client Quit]
fredl-pc has joined #linux-sunxi
IgorPec has joined #linux-sunxi
chewitt has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
nuuuciano has quit [Ping timeout: 264 seconds]
qeed has quit [Quit: Leaving]
chewitt has quit [Quit: Adios!]
DullTube has joined #linux-sunxi
montjoie has joined #linux-sunxi
Saurabh has joined #linux-sunxi
Saurabh has quit [Client Quit]
kristina has quit [Ping timeout: 240 seconds]
kristina has joined #linux-sunxi
yann|work has quit [Ping timeout: 240 seconds]
<wens>
fredl_: BROM does not output anything
anarsoul has quit [Remote host closed the connection]
anarsoul has joined #linux-sunxi
AneoX has joined #linux-sunxi
AneoX_ has quit [Ping timeout: 248 seconds]
benettig_ has joined #linux-sunxi
hlauer has joined #linux-sunxi
benettig has quit [Ping timeout: 256 seconds]
f0xx has joined #linux-sunxi
clemens3_ has joined #linux-sunxi
kever has joined #linux-sunxi
yann|work has joined #linux-sunxi
xyntrix has joined #linux-sunxi
reinforce has joined #linux-sunxi
f0xx has quit [Ping timeout: 268 seconds]
matthias_bgg has joined #linux-sunxi
msimpson has joined #linux-sunxi
leio has quit [Remote host closed the connection]
leio has joined #linux-sunxi
fkluknav has quit [Ping timeout: 268 seconds]
paulliu has joined #linux-sunxi
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
romainmahoux[m] has joined #linux-sunxi
hardfalcon has quit [Ping timeout: 248 seconds]
xyntrix has quit [Quit: Leaving]
xes has quit [Read error: Connection reset by peer]
hardfalcon has joined #linux-sunxi
hardfalcon has quit [Ping timeout: 256 seconds]
megi has quit [Ping timeout: 248 seconds]
fkluknav has joined #linux-sunxi
leviathan has joined #linux-sunxi
hardfalcon has joined #linux-sunxi
fkluknav has quit [Ping timeout: 248 seconds]
nuuuciano has joined #linux-sunxi
afaerber has quit [Quit: Leaving]
steev has quit []
steev has joined #linux-sunxi
afaerber has joined #linux-sunxi
zerotri has quit []
zerotri has joined #linux-sunxi
<fredl-pc>
hi wens, yeah I believe beeble told me that already yesterday, thanks.
focus has joined #linux-sunxi
benettig_ has quit [Quit: Leaving]
benettig has joined #linux-sunxi
IgorPec has quit [Ping timeout: 265 seconds]
<fredl-pc>
So I used buildroot....
<fredl-pc>
and it created an sdcard.img for me
<fredl-pc>
It's 131M large. When I copy that into DRAM with sunxi-fel... is there a way from u-boot to move that unchanged to the eMMS chip somehow?
<focus>
willmore: yes a lot more gates per sq mm. They even got Global Foundaries 14nm process :) - this the first time I hear of MOSIS because I be 80's graduate :(
<focus>
I saw SiFive mentioned somewhere, but since they started doing big (closed chips), i got no idea what they are about
<willmore>
You didn't get a chance to design a 1 micron rule part? :)
<focus>
no - will have to go to university or find $$ to fund a chip
<focus>
I want to make Digital Quantum CPU
<focus>
current von neuman is shiiiittte!
<fredl-pc>
Hmm I just did sudo ../sunxi-tools/sunxi-fel -v uboot u-boot-sunxi-with-spl.bin write 0x42000000 sdcard.img
<fredl-pc>
Shouldn't I then see the start of my sdcard.img when I do md 0x4200000 ?
<willmore>
fredl-pc, is DRAM initialized at that point?
<fredl-pc>
Doesn't the sunxi-fel write do that?
<willmore>
IIRC, no.
<fredl-pc>
How do I check/do that then?
<willmore>
That's part of the boot process as it requires board specific in fo.
* willmore
has never FEL booted a board, but has listened to dozens of people do it.
<fredl-pc>
well FEL boot in itself isn't so hard to do
<fredl-pc>
But what it ACTUALLY does under the surface is not so easy to figure out
<fredl-pc>
when I do 'strings sdcard.img' I DO see the eGON.BT0 bootsignature in that image
<fredl-pc>
Well, give or take, as I grabbed a bunch of stuff from other boards and tweaked where it seemed obvious
<fredl-pc>
(doing this on a board that's designed by our hardware dept.)
<fredl-pc>
See I'm not fully sure what write 0x42000000 sdcard.img does
<willmore>
Given my caution before, I would say that you need uboot to initialize dram before you can do that copy.
<willmore>
uboot seems to be the one that does the DRAM initialization these days.
<fredl-pc>
I don't know for sure where that image ends up then
<willmore>
It should copy the sdcard.img from your pc over the USB (via FEL) to the board and write it to DRAM at 0x42000000
<fredl-pc>
Except that sunxi-fel notably takes longer as it's copying 131MB somewhere
<willmore>
Yes.
<fredl-pc>
Got basically 2 questions therefore 1) where does it end up and 2) can I write it to our eMMC chip from u-boot somehow
<willmore>
Okay, looking back at your command, it looks like you are doing all of that. I guess my answer would be "yes, I would expect to see the image there".
<fredl-pc>
I guess I could boot a kernel instead
<willmore>
You have exausted my knowledge in this area, I'm afraid.
<fredl-pc>
pity, thanks for thinking along anyway :)
<willmore>
If you can boot a kernel, you can use USB gadget to get data to the board and then linux commands to write it to wherever.
<willmore>
fredl-pc, I'm glad to offer what little help I have to give. ;)
<fredl-pc>
if I could get USB gadget to work on this board that's be cool
<willmore>
Well, you've got working FEL and that's normally the hard step.
<willmore>
Enabling all of the proper settings in the kernel is step 2
<beeble>
fredl-pc: in u-boot, mmc write, or get gadget to work and use ums, or boot linux and use standard linux userland tools
<fredl-pc>
haha with this board....
<willmore>
Then loading all the rigth drivers is step 3.
<willmore>
Ahh, beeble knows way more!
<fredl-pc>
it's like it's trying to put a cat in the bathtub
<willmore>
Put the cat in before the water.
<fredl-pc>
lemme tell ya I've been in the mood to drown the cat instead :P
matthias_bgg has quit [Ping timeout: 265 seconds]
* willmore
can relate
<fredl-pc>
beeble - mmc write addr blk# cnt
<beeble>
exactly
<fredl-pc>
would addr be the address in DRAM?
<beeble>
yes
<fredl-pc>
okay gotcha
<beeble>
and blk# is the emmc block
<beeble>
and cnt is how many blocks
<fredl-pc>
oh...
<fredl-pc>
And to get the image in the right spot in eMMC, what blk# would I need?
<beeble>
your blocksize is 512 byte
<KotCzarny>
uboot (that eg0n part) goes from 8th sector
<fredl-pc>
as from what I understand BROM looks for eGON.BT0 in a very specific spot, correct?
<KotCzarny>
there are suspicions that secured brom looks for different location too
<fredl-pc>
so IF I had my sdcard.img copied into 0x42000000 with sunxi-fel....
<KotCzarny>
did you build and installed uboot on that img too?
<KotCzarny>
or its just rootfs?
<fredl-pc>
buildroot made it
<fredl-pc>
And buildroot seems to be compiling the whole internet, I'm not sure what all it put where tbh
<fredl-pc>
actually looking with 'strings' into it and I see