<rperier>
systemd works like a charm from the network but not from an usb key, I will investigate, in the worst case I can boot with a minimalistic init or with sysvinit probably
ganbold_ 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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<rperier>
it does not make sense it looks to a supply issue...
<naobsd>
supply more power to usb disk...
<rperier>
it is an usb stick... it is powered by the board directly
levd has joined #linux-rockchip
levd1 has quit [Ping timeout: 244 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
wildea01 has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 258 seconds]
wildea01 has quit [Ping timeout: 258 seconds]
wildea01 has joined #linux-rockchip
wildea01 has quit [Ping timeout: 255 seconds]
wildea01 has joined #linux-rockchip
wildea01 has quit [Ping timeout: 255 seconds]
wildea01 has joined #linux-rockchip
wildea01 has quit [Ping timeout: 264 seconds]
wildea01 has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
Tony_ has quit [Read error: Connection reset by peer]
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
levd1 has quit [Ping timeout: 264 seconds]
Avagetto has quit [Quit: Leaving.]
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
selfbg has quit [Quit: Leaving]
Avagetto has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
field^Mop has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
mrcan_ has joined #linux-rockchip
mrcan has quit [Ping timeout: 250 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
dlan has quit [Ping timeout: 258 seconds]
naobsd has quit [Quit: Page closed]
dlan has joined #linux-rockchip
cosm has quit [Ping timeout: 245 seconds]
cnxsoft1 has quit [Remote host closed the connection]
<AstralixNB>
naobsd, sorry got stuck in a different channel... Have a short question
<AstralixNB>
I am trying to build my own sd card images
<AstralixNB>
A basic investigation to understand the process shows...
cnxsoft has quit [Quit: cnxsoft]
<AstralixNB>
I use a radxa prebuild update.img for sd card and use the windows Rockchip Firmware Tool to write the image to the card and it boots.
<AstralixNB>
It goes through the full process of booting recovery, formatting, rebooting to fresh Android
<AstralixNB>
Now I use the same update.img and copy it via dd if=update.img of=/dev/mmcblk0 ...
<AstralixNB>
It boots into kernel and shows an initramfs minimal command line
<AstralixNB>
As it boots to kernel, the loader and parameter seems to work at least partly. But whatever it is, the Windows Firmware Tool does some magic to the update.img
<naobsd_>
update.img packed by rkImageMaker is not SD card image.
<AstralixNB>
I did not pack the image myself
<naobsd_>
SD Firmware Image makes bootable SD card from update.img
<naobsd_>
err
<naobsd_>
SD Firmware Tool makes bootable SD card from update.img
<AstralixNB>
Yes
<AstralixNB>
I just followed your rules: Do step by step, do exactly one step after the other
<AstralixNB>
I used a working prebuild update.img
<naobsd_>
I surprised that "dd if=update.img of=/dev/mmcblk0" booted.
<naobsd_>
I think you have initramfs minimal command line on NAND
<AstralixNB>
If you plug in SD the loader does not run any NAND.
<AstralixNB>
I had some logs and could clearly see that it bootet from sd. not NAND
<AstralixNB>
BUILD=====2
<AstralixNB>
SdmmcInit=0 0
<AstralixNB>
FwPartOffset=0 , 0
<AstralixNB>
If you boot from NAND, there is no line "SdmmcInit=0 0"
<naobsd_>
then you did something wrong...anyway, update.img is not SD card image
<AstralixNB>
ok, I wrote a simple bash script that does exactly what is described on that page.
<naobsd_>
but I don't have enough time to update info for now
<AstralixNB>
But then the loader tells me that there is no valid parameter to be read
<AstralixNB>
Ok, I have enough SD cards to give it several runs and then check myself.
<AstralixNB>
Just wanted to avoid double work
<naobsd_>
I have no idea what you exactly did
<AstralixNB>
very simple
<naobsd_>
I cannot answer why parameter is not found w/o info
<AstralixNB>
copyied loader parts to the given addresses
<AstralixNB>
copied parameter to offset 0x2000 and copied all other images with an offset of 0x2000 to the card
<naobsd_>
many info is still missing, but I guess you didn't do "rkcrc -k parameter parameter.img"
<AstralixNB>
I tried both.
<naobsd_>
"try both" is wrong.
<naobsd_>
RK header is always needed for parameter on storage
<AstralixNB>
I tried parameter first and it did not find any parameter
<AstralixNB>
then I did the rkcrc and flashed the parameter.img instead
<AstralixNB>
It gave several lines of images not found
<AstralixNB>
So there must be more to change until this sd card configuration is working
<naobsd_>
"It gave several lines of images not found" you said parameter is found?
lioka has joined #linux-rockchip
lioka has quit [Changing host]
<AstralixNB>
If you know rockchips error reports... It is not very self explaining
<naobsd_>
well
<naobsd_>
all I need is defail from you
<AstralixNB>
I am not sure if it wants to tell me that the parameter wasn't found at the expected offsets, or the images inside parameter
<naobsd_>
please answer, is parameter found with parameter.img?
<AstralixNB>
I have to reproduce that case first
<naobsd_>
is serial console output different when paramater (w/o rkcrc) and when parameter.img?
<AstralixNB>
probably yes
<AstralixNB>
I do have the log on a different machine
<naobsd_>
if "It gave several lines of images not found" it means boot recovery kernel etc, then paramater is found, but images in other partition are not found
<naobsd_>
again, detail info is needed to answer
<AstralixNB>
Do you know if the Windows tool does rewrite the sd-cards parameter content with different addresses, when it converts it to parameter.img?
<naobsd_>
currently no command/script info, no console output
<AstralixNB>
naobsd, you're one step ahead of my analysis. First step was to use a working sd-card image and try two ways of bringing it to the card.
<AstralixNB>
Result: Windows-Tool does some magic to the update.img before writing the content to the card
<AstralixNB>
Next step: check what is the result on the card and how does it differ from the original images.
<naobsd_>
sorry, I have to leave here now
<AstralixNB>
I do have forensics toolchain and report back
<AstralixNB>
Don't miss your train
<naobsd_>
what is done by windows tool is explained
<naobsd_>
(it's not perfect but explained some)
<AstralixNB>
I cross check and keep an eye on your work
<AstralixNB>
sure
<naobsd_>
parameter in update.img is already converted (have PARM header etc)
<naobsd_>
see you later
naobsd_ has quit [Quit: Page closed]
field^Mop has quit [Ping timeout: 240 seconds]
antoinemaillard has quit [Quit: antoinemaillard]
field^Mop has joined #linux-rockchip
antoinemaillard has joined #linux-rockchip
selfbg has quit [Quit: Leaving]
naobsd has joined #linux-rockchip
<naobsd>
at home now
<naobsd>
but I don't have so much time today, here is 0AM
field^Mop has quit [Ping timeout: 255 seconds]
<naobsd>
update.img is just for flashing tool, it's not same as actual structure on flash storage (NAND/SD/eMMC)
<naobsd>
think about (RK)AndroidTool and upgrade_tool, they can understand individual partition image
<naobsd>
parameter must have header etc on flash storage(NAND/SD/eMMC)
<naobsd>
some tools accept plain parameter (w/o header etc), they add header internally
<naobsd>
any tool doesn't modify parameter
<naobsd>
SD Firmware Tool should read partition info from parameter in update.img to know partition layout
<naobsd>
when write partition images to correct place
<naobsd>
you can read data written by SD Firmware Tool from SD card
<naobsd>
you can find header at sector 64/65, DDR blob at 68, loader at 92(actually it depends on the value in sector 64), parameter at 0x2000,
<naobsd>
you can find other partition images after 0x2000 with offset 0x2000
field^Mop has joined #linux-rockchip
<naobsd>
you can make same data structure with dd
<naobsd>
what you need is make it same
<naobsd>
if something is wrong, you'll get error
arokux has quit [Remote host closed the connection]
arokux has joined #linux-rockchip
Bludot has joined #linux-rockchip
Bludot has quit []
ssvb has quit [Quit: Leaving]
mrcan__ has joined #linux-rockchip
mrcan_ has quit [Remote host closed the connection]
field^Mop has quit [Ping timeout: 256 seconds]
field^Mop has joined #linux-rockchip
field^Mop has quit [Ping timeout: 250 seconds]
field^Mop has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
antoinemaillard has quit [Quit: antoinemaillard]
antoinemaillard has joined #linux-rockchip
bengal has joined #linux-rockchip
Avagetto has quit [Quit: Leaving.]
cosm has quit [Ping timeout: 255 seconds]
antoinemaillard has quit [Ping timeout: 265 seconds]
mrcan_ has joined #linux-rockchip
mrcan__ has quit [Ping timeout: 264 seconds]
gb_master has joined #linux-rockchip
cosm has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
mrcan_ has quit [Remote host closed the connection]
mrcan__ has joined #linux-rockchip
AstralixNB has quit [Quit: Leaving.]
mrcan_ has joined #linux-rockchip
mrcan__ has quit [Ping timeout: 256 seconds]
mrcan_ has quit [Remote host closed the connection]
mrcan__ has joined #linux-rockchip
AstralixNB has joined #linux-rockchip
AstralixNB1 has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
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
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
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
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
nighty-_ has quit [Quit: Disappears in a puff of smoke]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<field^Mop>
rperier: saw that wtf log of yours
<field^Mop>
rperier: looks quite ugly, i must say.
<field^Mop>
rperier: you already found some xplanation? interesting ext4 errs, though
<field^Mop>
rperier: it might nevertheless be a power supply problem. may well be that this usb device draws more than 500mA or the usb bus voltage or current is flaky (bad but possible)
<gb_master>
hello field^Mop... what did you mean with "non-cooperative USB-serial converters"?
<field^Mop>
rperier: and then.. this usb device manufacturer.. it's a phison device. maybe it is a _bad_ device in the sense of manipulated arm ctrler on the usb device that is handling the flash translation layer?
<field^Mop>
gb_master: hi
<field^Mop>
gb_master: that referred to chipsets obviously not being suitable to communicate with the rr device's uart
<gb_master>
all the PL2303 devices?
<field^Mop>
gb_master: there seems to exist some inverse predilection for pl2303 chipsets
<field^Mop>
gb_master: all those i got here fail to talk to the rr pro uart
<gb_master>
mmm
<field^Mop>
gb_master: strange, innit?
<gb_master>
you found a workaround?
<field^Mop>
gb_master: yes, used a raspi :)
<gb_master>
as a bridge?
<field^Mop>
gb_master: and now ordered some ftdi and silicon labs chip driven usb2serial converters from shenzen..
<field^Mop>
gb_master: hopefully they are authentic and no fakes as often the case with ftdi chips. we'll see to that when trying to talk at "high" uart speeds i guess
<gb_master>
hopefully :)
<gb_master>
and what about the wifi, in the end?
<field^Mop>
gb_master: kind of bridge. just ssh'd to the pi and used picocom from there to connect to the rr pro
<gb_master>
mmmmmm
<gb_master>
interesting
<field^Mop>
gb_master: oooh, well. that one is a big fail yet. no luck
<gb_master>
:S when I tried to use that, well... the whole Internet connection in my house was unstable
<field^Mop>
gb_master: i will investigate the staging driver, grekh already left a good number of todos in the tree for the rtl87xxau
<gb_master>
if you need any help, I'd like to contribute
<field^Mop>
gb_master: there's a whole lot left to do. but i don't complain. it's a challenge and you learn on the way. what's better than that (by means of IT at least ;)
<gb_master>
field^Mop: hehe, some kernel development would be anyway something to put on my resume :)
<field^Mop>
gb_master: oh, thanks. i will have the need to discuss one technical detail or the other, for sure.
<field^Mop>
gb_master: :) r8
<gb_master>
field^Mop: :)
<gb_master>
how did you connect RR's UART to the rpi?
<field^Mop>
gb_master: yet, i got already some good backlog on the mailinglist. 8-|
<field^Mop>
gb_master: hm, on the pi: rx(pin10), tx(pin8), gnd(pin6). connect pi's rx to rr's tx and vice versa, connect gnd (if you live on the cautious side then add a resistor in between to keep x-current at a minimum)
<gb_master>
I'll try right now
<field^Mop>
gb_master: hey, don't blame me for a blown pi or rr. :) you should verify those settings. i might err.
<gb_master>
field^Mop: I'm verifying, in fact :)
<field^Mop>
gb_master: thx :)
<field^Mop>
i start hating those little pis :(
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
<gb_master>
field^Mop: serial up and running
<field^Mop>
gb_master: nice!
bengal has quit [Ping timeout: 240 seconds]
<gb_master>
rperier?
rperier has quit [Remote host closed the connection]
hramrach_ has quit [Remote host closed the connection]
hramrach_ has joined #linux-rockchip
rperier has joined #linux-rockchip
rperier has joined #linux-rockchip
Bludot has joined #linux-rockchip
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
AstralixNB1 has quit [Ping timeout: 250 seconds]
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
gb_master has quit [Remote host closed the connection]