ChanServ changed the topic of #radxa to: http://radxa.com/ - Logs: http://irclog.whitequark.org/radxa
rperier_ has joined #radxa
ganbold__ has joined #radxa
minimec_ has joined #radxa
rperier has quit [Write error: Connection reset by peer]
minimec has quit [Ping timeout: 250 seconds]
ganbold_ has quit [Ping timeout: 250 seconds]
naobsd has joined #radxa
hipboi has joined #radxa
<naobsd> hipboi: kernels in recent(Aug) ubuntu images for both pro and full/lite were built from stable-3.0?
<naobsd> I want to update wiki pages which refer github
<hipboi> naobsd, yes
<hipboi> 14.04 images are built from the stable-3.0 kernel
<hipboi> naobsd, we can not use the name rock zero :(
<hipboi> naobsd, because we have made the stickers for the packaging
<naobsd> oh ;)
<hipboi> naobsd, so let distinguish them by adding the time
<hipboi> rock lite (mid 2014)
<naobsd> I see
<naobsd> ah, 1 more Q: recent _Android_ image still uses kernel source from SDK?
<hipboi> naobsd, android image still use the rock2014 kernel
<hipboi> we are still working on the tablet version of android
<naobsd> hipboi: thanks!
<naobsd> I compared SDK kernel and stable-3.0
<naobsd> and I felt headache ;)
<hipboi> naobsd, yes :(
<hipboi> i think you refer the SDK kernel is the box SDK
<hipboi> stable-3.0 is from the tablet SDK
<naobsd> ah, yes
<naobsd> you have tablet SDK too?
<hipboi> naobsd, yes
<hipboi> i am planning to push it to github
<hipboi> but so many trees...
<naobsd> I hope I can do more things from this month...my job is switched to new project at new place from today,
snkt has joined #radxa
rperier_ is now known as rperier
rperier has quit [Changing host]
rperier has joined #radxa
paowz has quit [Ping timeout: 240 seconds]
paowz has joined #radxa
<paowz> naobsd: Hi ! When I say "it must be.." it's just some assumptions, actually.. unlike "it has to be.." ;-) Anyway, you say there's not way to specify address for bootloader because it's just written to proper area.. Where is this area actually ?
<paowz> I mean, is this area on NAND or elsewhere (eeprom, whatever..) ?
<naobsd> I'm not Rockchip person, I don't know any "actual" info
<naobsd> I guess it's in NAND
<naobsd> well, probably, it's sure
<naobsd> because bootloader is not loaded if NAND is erased/forced to mask rom mode
<naobsd> sometimes it's referred as IDB
<naobsd> probably it can be read by upgrade_tool
<paowz> naobsd: ok, thanks.. and why do you say, we cannot specify an address ?
<paowz> I mean, through upgrade_tool, it looks possible to provide an address for buffer writes
<paowz> I'm justa dummy trying to figure out things :)
<naobsd> please explain, how can you specify address to flash bootloader?
<naobsd> well
<paowz> hold on.. :)
<naobsd> I know USB protocol
<naobsd> (part of)
<hipboi> i think upgarde_tool can specify the address
<hipboi> only the logical partition
<naobsd> and I'm sure there are some values like an address
<naobsd> yes, but bootloader is not in logical partition :)
<naobsd> and there is no physical information about NAND
<paowz> yep, I guess bootloader is not a logical partition.. (at least, unless we reach the kernel startup and its supplied MTD arguments..)
<paowz> look.. I just startup my RR Pro in MaskMode (because I screwed it some days ago..)
<paowz> ----------------Professional Command -----------------
<paowz> TestDevice:TD
<paowz> ResetDevice:RD
<paowz> ReadFlashID:RID
<paowz> ReadFlashInfo:RFI
<paowz> ReadChipInfo:RCI
<paowz> ReadSector:RS <BeginSec> <SectorLen> [-decode] [File]
<paowz> WriteSector:WS <BeginSec> <File>
<paowz> ReadLBA:RL <BeginSec> <SectorLen> [File]
<paowz> WriteLBA:WL <BeginSec> <File>
<paowz> EraseBlock:EB <CS> <BeginBlock> <BlokcLen> [--Force]
<paowz> -------------------------------------------------------
<naobsd> probably upgrade_tool rs(read sector) ws(write sector) can touch bootloader area
<paowz> here is part of upgrade_tool output..
<paowz> it seems we can access NAND by addressing it this way..
<naobsd> "bootloader is not a logical partition" is very sure
<paowz> I agree with it.. no problem..
<paowz> I really do.
<naobsd> why do you need address?
<paowz> because I basically wanted to flash a u-boot release (the one I found on Tom's website) to give it a try..
<naobsd> just flash it as bootloader
<paowz> you mean using '-p' parameter ?
<naobsd> parameter is not bootloader
<naobsd> upgrade_tool ul or db
<paowz> no, no.. sure, of course.. I mean DI -P blablabla
<paowz> DownloadImage:DI <-p|-b|-k|-s|-r|-m image> [parameter file]
<paowz> with -p parameter..
<naobsd> di is for logical partitions
<paowz> or -b..
<naobsd> parameter partition is also logical
<paowz> ok
<hipboi> the u-boot source code has the upgrading code
<naobsd> RK u-boot supports RK USB protocol
<naobsd> (and fastboot)
<naobsd> existing USB tools can be used with u-boot (if u-boot is properly working ;)
<paowz> another question.. I messed up my NAND flash.. what RR Pro image shall I use to get back to factory default ?? I'm lost when looking at http://wiki.radxa.com/Rock
<naobsd> I don't know what was default, but there are NAND images for Pro http://wiki.radxa.com/Rock/prebuilt_images
<paowz> http://wiki.radxa.com/Rock/unbrick refers to update.img..
<paowz> hipboi: ok.. so I'm in MaskMode mode, I shall be able to get back a functional RR..
<paowz> I give it a try right away.. :)
<naobsd> xxxx_update.img is referred as just "update.img"
<paowz> ok
<naobsd> probably file naming, image type, proper tool need to be explained...
<naobsd> *.img is too generic ;)
<hipboi> and "update" is too generic...
<paowz> ..or I might a bit perfectionist upon namings.. as I'm expecting something accurate ;)
<paowz> I don't want to do some "nit pickin'" I mean xD
<naobsd> maybe: forNAND/*_nand.img/USBtool, forSD/*_sdcard.bin/dd, rootfs/*_rfs.ext4/dd
<paowz> that would be a good idea, indeed..
<hipboi> ok, it's decided
<paowz> *champagne* ;)
<naobsd> probably something like "*_nand.img is typically referred as update.img, i.e. whole NAND image" need to be explained...
<paowz> http://pastebin.com/EbpS1wvN somebody has reached the bootloader prompt within barebox..
<naobsd> I think it's not "news"
<naobsd> when I tried barebox on RR, it supports only ethernet
minimec_ has quit [Quit: Lost terminal]
<naobsd> it's very useful to load kernel/etc from network
<paowz> :)
<paowz> I wanted to use uboot to get NFS support.. and work on a rootfs that was not on the target..
BorgCuba has joined #radxa
<BorgCuba> noabsd, is the barebox code available somewhere?
<naobsd> please see http://www.barebox.org/
<BorgCuba> okay, thanks! :-)
naobsd has quit [Quit: Page closed]
snkt has quit [Quit: Leaving]
BorgCuba has left #radxa [#radxa]
chens has joined #radxa
chens has quit [Ping timeout: 246 seconds]
BorgCuba has joined #radxa
FreezingCold has quit [Ping timeout: 240 seconds]
FreezingCold has joined #radxa
FreezingCold has quit [Ping timeout: 245 seconds]
FreezingCold has joined #radxa
FreezingAlt has joined #radxa
FreezingCold has quit [Ping timeout: 245 seconds]
BorgCuba has quit [Quit: leaving]
bengal has joined #radxa
bengal has quit [Changing host]
bengal has joined #radxa
qloogkm_ is now known as qloogkm
FreezingAlt has quit [Ping timeout: 260 seconds]
FreezingAlt has joined #radxa
Bludot has joined #radxa
FreezingAlt has quit [Ping timeout: 245 seconds]
FreezingAlt has joined #radxa
bengal has quit [Ping timeout: 245 seconds]
FreezingAlt has quit [Quit: Out]
FreezingAlt has joined #radxa
zombu2 has quit [Ping timeout: 240 seconds]