cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-rockchip
naobsd has joined #linux-rockchip
naobsd has quit [Read error: Connection reset by peer]
naobsd has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
naobsd has quit [Ping timeout: 252 seconds]
naobsd has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
<sjoerd>
mmind00: rk3288
<sjoerd>
got the thing to load one of the binaries now from the radxa repo over maskrom
<sjoerd>
now trying to put on custom u-boot to the emmc which is being specail
markm_ has quit [Ping timeout: 265 seconds]
markm_ has joined #linux-rockchip
markm_ has quit [Ping timeout: 260 seconds]
<naobsd>
ah, sorry & thanks for emac issue, I couldn't get free time at all :(
<sjoerd>
naobsd: i'm having some oddities with mask rom mode, is there any way i can make it write something on "flash" (which is emmc on this board) at an offset of 32k ?
premoboss has quit [Ping timeout: 265 seconds]
<naobsd>
sjoerd: RK tools such as upgrade_tool/AndroidTool.exe can do it
dlezcano has quit [Read error: Connection timed out]
<naobsd>
sjoerd: but you need to prepare RKLoader.bin form binary for such tools
<naobsd>
or if you can run Linux on target board, you can write data to emmc via Linux environment
dlezcano has joined #linux-rockchip
<sjoerd>
Right, i'm just looking at a way to put a proper u-boot on a board without jumping through hoops
<naobsd>
btw upstream u-boot supports writting data to (e)mmc?
<sjoerd>
naobsd: i've gone to maskrom mode and loaded rk32xxminiloaderall.bin but that doesn't seem to do the trick
<naobsd>
fastboot on u-boot may be helpful if it works
<naobsd>
well
<sjoerd>
naobsd: upstream u-boot also has some other flashing capabilities
<naobsd>
download miniloader.bin from mask rom mode, then flash your_own_loader.bin
<naobsd>
is not working?
<sjoerd>
doesn't seem so
<sjoerd>
I did some tricks to put some known data on the eMMC at the offset i care about (iotw 32k where i want to put the SPL) but rkflashtool r doesn't seem to be able to read that
<naobsd>
well
<naobsd>
rkflashtool doesn't support loader area
<naobsd>
I said use RK tools such as upgrade_tool for flashing loader
<sjoerd>
Right that wasn't entirely clear to me
<sjoerd>
ooi do you know what would be needed to flash to loader area ?
<naobsd>
rkflashtool can do "download loader code to SRAM/DRAM" but cannot do "flash it to NAND/eMMC/etc"
<naobsd>
well
<sjoerd>
rkflashtool w doesn't put stuff on flash ?
<naobsd>
"rkflashtool w" can flash images to logical area/partition
<naobsd>
loader is not in logical area/partition
<naobsd>
loader flashing protocol should be almost known, but it needs ECC calculation.
<sjoerd>
right but w <offset> <size> is a bit more flexible it seems
<naobsd>
in addition to dada part, oob part need to be sent
<naobsd>
well
<sjoerd>
I see
<naobsd>
no
premoboss has joined #linux-rockchip
<naobsd>
[ loader area | logical partitions ]
<naobsd>
"rkflashtool w" is for logical area
<naobsd>
on eMMC, loader area is 0-2047th sector, logical area is 2048-th sector
<sjoerd>
Right
<naobsd>
rkflashtool r|w 0 read/write sector 2048th on eMMC
<sjoerd>
I see
<naobsd>
rkflashtool r|w doesn't support loader area clearly
<sjoerd>
interestingly it looks like rkflashtool i does get my bits
<naobsd>
USB protocol is different
<naobsd>
"rkflashtool i" is for loader area
<naobsd>
ah sorry, loader area should be started from 64- sector on eMMC
<naobsd>
loader area a.k.a. IDB
<naobsd>
for writing loader, we need ecc code
<naobsd>
probably.
<naobsd>
(for eMMC it may not be required)
<sjoerd>
Looking at what rkflashtool i retrieves the ecc on eMMC is just all 0xff
<naobsd>
I guess, for eMMC, ecc things should be done in chip
<sjoerd>
yeah
<sjoerd>
I'll havea go at implement rkflashtool j
<naobsd>
then we can send random oob data
<sjoerd>
for emmc iotw just fill the ecc chunk with 0xff
<sjoerd>
ack
<philhug>
just a quick question: rkflashtool is still the most commonly used tool right? I just packaged it for Debian and would upload it soonish..
<sjoerd>
philhug: Looking forward to having that in debian ;)
<sjoerd>
philhug: are you loking at also enabling u-boot/kernel in debian (it's somewhere on my backlog but...)
<philhug>
sure, I can do that as soon as everything needed is upstream.
<sjoerd>
should be for rk3288
<sjoerd>
what boards are you interested in ?
<naobsd>
(rkflashtool needs some refactoring, but I have no time...)
<naobsd>
(now trying my terrible node.js based RK compatible OTA server...)
<naobsd>
I hope it's better than tomcat-based RK original OTA server ;)
<naobsd>
RK OTA download client must be XXXX
<philhug>
sjoerd: I'm insterested in rk3288/chromebook
<naobsd>
oh, chromebook loader shouldn't support rock usb protocol...
<naobsd>
well
<philhug>
and I have an old tv stick with rk3066
<philhug>
which is why I packaged it quickly
<naobsd>
rkflashtool should work _on_ rk3288/chromebook too ;)
<philhug>
naobsd: really?
<naobsd>
ah sorry
<naobsd>
linux on chromebook
<naobsd>
libusb is required, I'm not sure chromeos has it
<philhug>
ah you mean on chromeos?
<naobsd>
it should work on linux on chromebook, it may work on chromeos on chromebook
<naobsd>
I don't have any chromebook
<naobsd>
permission might not be given
<naobsd>
anyway rkflashtool should be portable
<naobsd>
it should work on Android too ;)
<philhug>
yes, it seems very easy to port. but I only need it on Linux atm :)
<mmind00>
naobsd philhug: the regular protocol spoken by rkflashtool (aka r and w options) is specific to the rockchip uboot ... I don't think coreboot (used on Chromebooks) speaks that protocol
<naobsd>
it will not be implemented to upstream u-boot too... at least I have no interest...
<sjoerd>
the protocol is too vendor specific to make sense for upstream
<naobsd>
but I will maintain rkflashtool as much as possible :)
<philhug>
yes sure it depends on the proprietary loader
<sjoerd>
Upstream would use either fastboot or dfu which is more sensible there :)
<philhug>
it could make sense though to have a tool that speaks the mask rom protocol.
<mmind00>
philhug: I guess bootloader is a matter of taste ... so far I didn't find coreboot lacking anything ... including dualbooting either chromeos from emmc or debian from sd-card
<sjoerd>
does an initramfs work now in the fit images ?
<mmind00>
hmm, ok that might be one issue, when trying to boot a real generic kernel
<sjoerd>
I like the u-boot approach as that makes the distro integration a bit simpler and more generic
<sjoerd>
though i'm slightly biased :)
<philhug>
just wanted to ask the same. I need dtb appended and initrd support
<sjoerd>
the coreboot/verified boot stuff from chromeos is quite cool
<philhug>
s/initrd/initramfs
<mmind00>
philhug: coreboot/fit does have a separate section for the dtb(s) ... one fit image can boot multiple different machines
<sjoerd>
nod
<sjoerd>
and the fit image can in principle include the initrd as well
<sjoerd>
but i had issues with that on some samsung chromebooks way back
<mmind00>
when Kevin was integrating his Chromebook into the board-farm, the initramfs question also came up
<philhug>
mmind00: well, the Debian kernels use appended dtb's, so I don't have a choice there.
<philhug>
I'm more worried about initramfs
<sjoerd>
philhug: debian kernels don't use appended dtbs...
<sjoerd>
that only means that it's supoprted though
<philhug>
sjoerd: I'll try. but do you have an idea about initramfs?
<sjoerd>
you'd have to try, the samsung chromebooks didn't even use coreboot (their flash has u-boot) so it's likely it would work for corebook just fine
premoboss has quit [Ping timeout: 272 seconds]
ssvb has joined #linux-rockchip
<rperier>
hi all
bludot has joined #linux-rockchip
premoboss has joined #linux-rockchip
dlezcano has quit [Read error: Connection timed out]
cnxsoft has quit [Quit: cnxsoft]
cristian_c has joined #linux-rockchip
naobsd has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 260 seconds]
<ganbold>
naobsd: ping
<naobsd>
ganbold: hi
<ganbold>
naobsd: hi
<ganbold>
naobsd: trying to flash kernel to RR board
<ganbold>
rkflashtool: info: Error: Partition 'kernel' not found.
<mmind00>
c0d3z3r0: I would've thought so, as it was only something I identified as potential problem by looking at the code :-) ... my change probably doesn't solve it wholly
<c0d3z3r0>
mmind00: ok, thank you anyway :)
dlezcano has quit [Read error: Connection timed out]
GriefNorth has quit [Ping timeout: 272 seconds]
dlezcano has joined #linux-rockchip
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
Sadneophyte has joined #linux-rockchip
johnnyr has joined #linux-rockchip
dlezcano has quit [Ping timeout: 252 seconds]
Sadneophyte has quit [Read error: Connection reset by peer]
bludot has quit [Quit: Connection closed for inactivity]
cristian_c has quit [Quit: Bye]
bludot has joined #linux-rockchip
Sadneophyte has joined #linux-rockchip
akaizen has joined #linux-rockchip
Sadneophyte has quit [Read error: Connection reset by peer]
naobsd has quit [Remote host closed the connection]
akaizen has quit [Remote host closed the connection]