Bludot has quit [Quit: Connection closed for inactivity]
vinceh has quit [Quit: Leaving]
Bludot has joined #radxa
paowz has joined #radxa
paowz has quit [Read error: No route to host]
paowz has joined #radxa
paowz is now known as PaowZ_afk
bengal has joined #radxa
FreezingCold has quit [Ping timeout: 246 seconds]
FreezingCold has joined #radxa
bengal has quit [Ping timeout: 264 seconds]
patronus has joined #radxa
Bludot_ has joined #radxa
rperier_ has joined #radxa
Bludot has quit [Ping timeout: 260 seconds]
patronus_ has quit [Ping timeout: 260 seconds]
mrueg has quit [Ping timeout: 260 seconds]
rperier has quit [Ping timeout: 260 seconds]
rperier_ is now known as rperier
rperier has quit [Changing host]
rperier has joined #radxa
Bludot_ is now known as Bludot
mrueg has joined #radxa
Bludot has quit [Quit: Connection closed for inactivity]
CosmicDuck has joined #radxa
bengal has joined #radxa
PaowZ_afk has quit [Ping timeout: 245 seconds]
FreezingCold has quit [Ping timeout: 240 seconds]
FreezingCold has joined #radxa
jnm has joined #radxa
paowz has joined #radxa
jnm has quit [Quit: leaving]
<
paowz>
does any of you have ever flash u-boot as a bootloader?
bengal has quit [Ping timeout: 245 seconds]
bengal has joined #radxa
afm has joined #radxa
<
bengal>
paowz: yes, I flashed u-boot
<
paowz>
bengal, you had some good results ? it works as expected ?
<
bengal>
I remember that the support was very basic, it was some months ago
<
paowz>
ok.. I mean, as long as it launches your kernel..
<
bengal>
anyway, you can always recover the board shorting the pins on nand
<
paowz>
yes indeed..
<
paowz>
what tool did you use to flash ? rkflashkit or upgrade_tool ??
<
bengal>
rkflashkit
<
paowz>
I'd like to understand how these tools know the flash address where to flash..
<
bengal>
if you want to try, there is a basic support for barebox (another bootloader similar to u-boot)
<
bengal>
(only as a second-stage bootloader)
<
paowz>
yep, I use barebox at work..
<
paowz>
I got interested into u-boot for the radxa mod..
<
paowz>
maybe you can help to find out why it is written not to flash the .bin at this page..
<
paowz>
bengal: they say "DON'T FLASH IT"
<
bengal>
I don't know
* bengal
searching the logs
<
bengal>
I don't remember if it could boot a kernel
<
paowz>
looks to be lot of errors around i2c
<
paowz>
it could not find partitions, apparently.. weird..
<
paowz>
and at the time you experimented that, you don't remember if you could actually start the kernel ?
<
bengal>
I was only looking at low level initialization, because I wanted to add it to barebox
<
bengal>
but then I found that it uses a binary blob for ddr initialization
<
paowz>
a binary blob.. hence, closed sources..
<
paowz>
interesting.. so you think, we're stuck with the proprietary bootloader from RockChip ?
<
bengal>
I think so
<
bengal>
until Rockchip decides to opensource the bootloader
<
bengal>
they started contributing to the linux kernel... maybe they will open the bootloader as well
<
paowz>
they started recently ?
<
paowz>
they wish to add their ARMv7 to mainline kernek ?
<
bengal>
a couple of months maybe
<
paowz>
very recent..
<
paowz>
question concerning flash tools.. where do they get flash addresses for flashing ?
<
paowz>
for instance, rkflashkit propose severals partitions, depending of your parameter files..
<
paowz>
does it mean it reads the file content to get to know the partitions addresses and sizes ?
<
bengal>
sorry, I don't know
<
paowz>
when I used to flash, I used to provide an address (whatever flash type you got, top-bottom or bottom-top)
<
paowz>
Loading partition information
<
paowz>
MACHINE_MODEL:radxa_rock
<
paowz>
MANUFACTURER:RADXA
<
paowz>
MAGIC: 0x5041524B
<
paowz>
MACHINE_ID:007
<
paowz>
ATAG: 0x60000800
<
paowz>
MACHINE: 3066
<
paowz>
CHECK_MASK: 0x80
<
paowz>
KERNEL_IMG: 0x60408000
<
paowz>
#RECOVER_KEY: 1,1,0,20,0
<
paowz>
#CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init mac_addr=de:ad:de:ad:be:ef initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)
<
paowz>
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),0x00E00000@0x00A000(linuxroot)
<
paowz>
my guess is these tools get partition information by reading the partition containing parameter file..
<
paowz>
what if I wipe this partition..
<
bengal>
I suppose that uses kernel partitions specified in parameters file
<
bengal>
probably it's not a good idea to erase it :)
<
paowz>
it must be within one of these partitions..
<
paowz>
rk29xxnand:0x00002000@0x00000000(parameter)
<
paowz>
yes.. apparently, parameter file is contained in the first partition referenced as "misc" by Radxa..
<
paowz>
this partition is being read by flash tools to get to know where to flash.
<
paowz>
and indeed, erasing it would be a bad idea..
<
bengal>
maybe the tool can always rewrite the parameter file
<
bengal>
at a fixed location
<
paowz>
I don't see this option in rkflashkit.. let me see in upgrade_tool..
<
paowz>
there is no such option to do so.. but you can achieve the same by using raw flashing..
<
paowz>
I mean WriteSector address, file blablabla..
<
paowz>
..at 0x00002000, nowhere else..
<
paowz>
bengal: ok.. gotta go.. nice to talk with you ;) see ya !!
bengal has quit [Quit: Leaving]
paowz has quit [Remote host closed the connection]
c0d3z3r0 has quit [Ping timeout: 240 seconds]
c0d3z3r0 has joined #radxa
FreezingCold has quit [Ping timeout: 240 seconds]
FreezingCold has joined #radxa
Travis_ has joined #radxa