<rperier>
that's weird but... in dwc2 I get a NULL hsotg->regs in dwc2_is_controller_alive(), so there is a page fault and kernel crashes as it is a fault from a interrupt context. The strange thing being that from dwc2/platform.c seems to initialiazed hsotg->regs AFTER devm_request_irq.... so technically an interrupt might be emitted before hsotg->regs is set... (I am still investigating)
<rperier>
last changes in dwc2 seem to have introduced bugs...
<rperier>
the nice thing being that theses ones are not really deterministic :D
<rperier>
naobsd: that's in the case like this one where you understand the power of git :)
<naobsd>
oh, it failed :(
<naobsd>
kernel history has invalid entry...
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
<AstralixNB>
Hi naobsd, even tried prebuild images with same result, so I guess it doesn't make a differenc to switch compilers
AstralixNB has quit [Ping timeout: 250 seconds]
selfbg has quit [Quit: Leaving]
nighty-_ has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
arokux has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 1.0.1]
RayFlower has joined #linux-rockchip
<AstralixNB>
Someone a hint how to create a mainline kernel boot.img?
<AstralixNB>
I thought it would be the same way as the usual boot.img
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cnxsoft1 has quit [Quit: cnxsoft1]
<rperier>
AstralixNB: 1)° Build your zImage, 2)° build your dtb, 3)° Concatenate the dtb at the end of the zImage and then create a boot.img with mkbootimg
field^Mop has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<mmind00>
rperier: I think AstralixNB did try that ... but hit an issue somewhere with the image not booting or something
<AstralixNB>
mmind00, rperier: just wanted to verify that this is the right way to proceed.
<AstralixNB>
The only thing I changed was not to include the initramfs in the kernel, so I cleared that setting in the menuconfig
<AstralixNB>
However, havin initramfs or not... the kernel should at least print some debug, in my case it doesn't give any output...
<AstralixNB>
If checked for earlyprintk and debug set to RK32 USART2
<AstralixNB>
According schematics, this is the correct UART for debug
<rperier>
does your uboot work ? have you access to a command line interface or something ? (I just try to understand the problem steps by steps)
<rperier>
(uboot provides a "mini shell" if I remember correctly)
field^Mop has quit [Ping timeout: 250 seconds]
<AstralixNB>
I used this uboot to boot some kernels. And that worked so far as I wrote yesterday.
<AstralixNB>
But I cannot intercept uboot by serial console. It is directly trying to boot the kernel and every 4..5 round it manages to boot the kernel up to the init of the fb devices.
<AstralixNB>
This looks a bit like there is a voltage problem... may be the uboot doesn't setup the DC/DC correctly?
GriefNorth_ has joined #linux-rockchip
<AstralixNB>
recompiled uboot with console enabled and I can access the console
<AstralixNB>
GNU ld (GNU Binutils for Ubuntu) 2.24
<AstralixNB>
hmm... there is no pmic available
<AstralixNB>
rkboot # pmic list
<AstralixNB>
PMIC devices:
<AstralixNB>
name: <NULL> bus: I2C_0
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
cyrozap has quit [Ping timeout: 240 seconds]
<AstralixNB>
Ok, checked some details in the schematics and the mainline rk3288-sdk-act8846.dts...
<AstralixNB>
The voltages are not matchint the table of the schematic.
<AstralixNB>
For instance voltage of DDR is 1.2V but table sayr 1.5V
<AstralixNB>
The schematic in addition mentions two separate DC/DC regs for VDD_CPU and VDD_GPU, these chips are silergy syr82x but these seem not to be supported in mainline.
<AstralixNB>
If the schematics match the board (I still have some daubts) there are good reasons why the firefly behaves in such a random way.
<AstralixNB>
But some of the values of the firefly kernel 3.10 dts voltage entries are not matching the ones in the schematics too...
<rperier>
according to what you said and to your post of the firefly's forum, I think that I will backup my emmc when I will receive the board, just in case (before start hacking)
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
ssvb has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
antoinemaillard has quit [Quit: antoinemaillard]
GriefNorth_ has quit [Quit: WeeChat 1.0.1]
RayFlower has joined #linux-rockchip
dlezcano has quit [Quit: Leaving]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
dlezcano has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 258 seconds]
apritzel has quit [Ping timeout: 250 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
gb_master has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
cyrozap has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
mrcan has quit [Remote host closed the connection]
mrcan_ has joined #linux-rockchip
gb_master has quit [Remote host closed the connection]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 240 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
RayFlower has quit [Quit: RayFlower]
<amstan>
how is everyone?
<naobsd>
u-boot almost does nothing for pmic
<naobsd>
u-boot/kernel should work as is
<naobsd>
what you need to do 1st is checking hardware before tying to start hacking
<naobsd>
ah, sorry, I'm talking about firefly
<naobsd>
no need to make backup
<naobsd>
if flashed image is broken, just reflash official image
nighty-_ has quit [Quit: Disappears in a puff of smoke]