<enkoder>
as opposed to the T760 that most rk3288 chips have?
<enkoder>
Pretty interesting. I didnt know rockchip had different skus for the 3288 chip
<enkoder>
"Rockchip Quad-Core RK3288C Processor"
<naobsd>
RK3288C is used for chromebook too
<naobsd>
chromebook spec says GPU is T724
<naobsd>
I don't know difference between RK3288 and RK3288C (I guess no difference at least for software)
nighty-_ has quit [Ping timeout: 260 seconds]
hipboi_ has quit [Quit: Leaving]
hipboi has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 260 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
levd1 is now known as levd
nighty^ has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 255 seconds]
levd1 is now known as levd
nighty^ has quit [Ping timeout: 265 seconds]
<aborche>
morning!
hipboi has quit [Ping timeout: 246 seconds]
hipboi has joined #linux-rockchip
nighty^ has joined #linux-rockchip
vickycq has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 272 seconds]
levd1 is now known as levd
hipboi has quit [Read error: Connection reset by peer]
premoboss has quit [Remote host closed the connection]
hipboi has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
levd1 is now known as levd
hipboi has quit [Read error: Connection reset by peer]
wadim_ has joined #linux-rockchip
wadim__ has joined #linux-rockchip
wadim__ has left #linux-rockchip [#linux-rockchip]
wadim__ has joined #linux-rockchip
wadim__ has quit [Client Quit]
hipboi has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
Ueno_Otoko has quit [Remote host closed the connection]
<mmind00>
enkoder naobsd: that's probably only a typo on the asus website ;-)
hipboi has joined #linux-rockchip
Ueno_Otoko has joined #linux-rockchip
levd1 has joined #linux-rockchip
steev has quit [Ping timeout: 240 seconds]
naobsd has quit [Quit: naobsd]
hipboi has quit [Read error: Connection reset by peer]
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
hipboi has joined #linux-rockchip
steev has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
steev has quit [Ping timeout: 246 seconds]
<aborche>
i'm confused :( kernel from radxa and kernel from linaro is very different. this make me crazy :(
* sjoerd
didn't know linaro did rockchip these days
<aborche>
guys which kernel the best choice for rk3188 ? i mean 3.10 branch. for porting chromebook or lollipop
hipboi has joined #linux-rockchip
<aborche>
linaro remove all rockchip includes from own kernel
<aborche>
o! hipboi. are you here ?
<aborche>
and i'm not sure for radxa kernel 3.10. in radxarocklite config for kernel 3.18.11, i cannot find any words about pwm which used for this board
<sjoerd>
rperier: any luck with the network stuff?
steev has joined #linux-rockchip
levd1 has joined #linux-rockchip
<aborche>
just for info. driver for rtl8723bs version 4.3.12 from sunxi repo is more stable than 4.2.5 for kernel 3.0.36+
levd has quit [Ping timeout: 272 seconds]
levd1 is now known as levd
<aborche>
rtk uart bluetooth is working too over rtk_hciattach. but in rabian bluez broken. in linaro vivid the same bluez package work ok
<rperier>
sjoerd: I did not retry since yesterday, no. I use a cross-link but it worked fine with my firefly on linux... so technically, it should work too...
<rperier>
sjoerd: well, I will investigate because ethernet with u-boot is so useful... I need it
<sjoerd>
rperier: Yeah it should work, just want to mimiize the variables
<sjoerd>
if you can try a gigabit switch tat would be interesting as well as the default clock setup is good for gigabit
<sjoerd>
rperier: One thing to note is that my patches do only the minimal set of changes on the clock setup (the default are mostly right).. The pinmuxing is more involved though
<sjoerd>
maybe there is a fierfly/rock difference i overlooked in the setup that's hurthing you though
<sjoerd>
pinmuxing would be the first thing to indeed look at
Omegamoon has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 260 seconds]
levd1 is now known as levd
<Omegamoon>
anyone in here having any experience updating the partitioning schema from recovery?
<Omegamoon>
whenever I update the Parameter partition from recovery I end up with flash read errors like:
<Omegamoon>
FlashReadRetry error!!,row = 21c20
<Omegamoon>
it is driving me nuts :S
<hipboi>
aborche, is there any reason i shouldn't be here :)
<aborche>
:)
levd has quit [Ping timeout: 255 seconds]
<aborche>
hipboi say me please as developer a very good board with rk3188t. do you run kernels greater than 3.0.36+ at radxa rock lite with all working features ?
<aborche>
i need make a choice. use rk3188 sticks for own project or move to sunxi
<aborche>
or rpi
<hipboi>
aborche, depends your requirement
<aborche>
rk3188 for me is a best choice. but i'm not sure about very old kernel which used everywhere.
wadim_ has quit [Remote host closed the connection]
ckeepax has joined #linux-rockchip
naobsd has joined #linux-rockchip
vickycq has joined #linux-rockchip
vickycq has quit [Client Quit]
vickycq has joined #linux-rockchip
maz__ has quit [Ping timeout: 250 seconds]
<naobsd>
because that was incomplete...
maz__ has joined #linux-rockchip
Ueno_Otoko has quit [Ping timeout: 240 seconds]
maz__ has quit [Ping timeout: 240 seconds]
maz__ has joined #linux-rockchip
<enkoder>
Hey guys, I am trying to learn more about the rockchip bootloaders for the radxa rock 2 (rk3288). From what I understand the bootloader is "proprietary", but is really just a custom u-boot that is looking for specific partitions in memory regions. The USB OTG loader won't take my compiled version of u-boot so where do I get information on the firmware upgrade USB OTG protocol?
<naobsd>
enkoder: "The USB OTG loader won't take my compiled version of u-boot so where do I get information on the firmware upgrade USB OTG protocol?" I cannot understand this part
<naobsd>
enkoder: do you want to know about usb protocol in proprietary loader?
<enkoder>
Yes thanks for following up, let me explain. When I use the upgrade_tool db or ul command on mainline u-boot, it says cannot find loader and will not let me flash the binary
<naobsd>
mainline u-boot doesn't know rockchip proprietary usb protocol
<naobsd>
you cannot use any flashing tool from RK which talks proprietary protocol
<enkoder>
Ah ok so its the USB protocol that is causing trouble. Seems like it should just take a binary and load it into a specific region of flash
<enkoder>
Hypothetically, if this board had jtag access I could flash the emmc on my rock2 with jtag or a programmer with mainline u-boot and it would boot right?
<naobsd>
I have no idea about jtag with RK SoCs
<naobsd>
I guess mainline u-boot mmc subsystem is able to write data to media
<naobsd>
well
<naobsd>
what do you want, writing mainline u-boot to emmc, or writing something to emmc with mainline u-boot?
<enkoder>
Both actually. I am ramping up on embedded linux really and I am trying to fully understand the stack.
<enkoder>
ts a daunting task but its really fun so far
<enkoder>
Sure. Can you briefly tell me what the upgrade_tool does? Specifically the download bootloader and upgrade loader commands do? Are they writing binaries to a specfic address on the emmc?
<naobsd>
detail is not documented
<naobsd>
I think,
<naobsd>
well
<enkoder>
bummer
<enkoder>
I did see the rkflashtool
<naobsd>
not documented but we can see what happen
<enkoder>
looks like someone reverse engineered it
<naobsd>
db pushing code to ram
<naobsd>
well
<enkoder>
sram or ram?
<naobsd>
both
<enkoder>
ok
<enkoder>
ul going to flash then?
<enkoder>
So whats your involvement with linux-rockchip? I see your name often
<enkoder>
BTW I appreciate the help youve given to me and others on this channel
<naobsd>
well
<naobsd>
I reversed some of usb protocol
<naobsd>
RK binary (RK3xxxLoader.bin) has 4 data
<naobsd>
2 set of "one for SRAM, another for DRAM"
<naobsd>
1set is for loading from OTG, another set is for flashing to on-board flash
<naobsd>
well
<enkoder>
Just copies of the same data
<naobsd>
1set is for loading from OTG, another set is for loading from on-board flash (i.e. flashing)
<naobsd>
it's possible to use 4 different code
<naobsd>
usually RK uses same code for SRAM, different code for DRAM
<naobsd>
DRAM code for loading from OTG is just for updating flash memory, DRAM code for loading from flash memory is for general booting
<enkoder>
gotcha
<naobsd>
probably "upgrade_tool db" just pushes SRAM/DRAM code for loading from OTG
Astralix has left #linux-rockchip [#linux-rockchip]
<enkoder>
Yeah looks like it. upgrade_tool db only works for me when I do an "upgrade_tool ef" first
<naobsd>
"upgrade_tool ul" (and some other commands which updates loader part) pushes SRAM/DRAM code for flash memory to flash memory
<enkoder>
So maybe db is flahsing sram, which gets loaded into dram by the romboot
<naobsd>
well
<naobsd>
SoC needs to be in "mask rom mode" for pushing SRAM/DRAM code from OTG
<enkoder>
One thing I am noticing thats interesting is there's two versions of u-boot in the boatloader? I see in the boot text from the uart, "U-Boot 2014.10-RK3288-02 (Jan 21 2015 - 17:07:53)
<enkoder>
" and another "#Boot ver: 2015-01-21#2.17
<enkoder>
"
<naobsd>
SRAM code (which initialize some first things and DRAM) need to be pushed at first
<enkoder>
this is on the RK3288Loader\(L\)_V2.17.bin bootloader
<enkoder>
Hey I gotta run, thanks for the help naobsd. I'm sure we will be in contact again.
<naobsd>
single loader has one u-boot version number and one RK loader version number
<naobsd>
rkflashtool l/L is for loading SRAM/DRAM code from OTG
<naobsd>
"flashing" protocol for "upgrade_tool ul"/"rkflashtool j" is implemented only in RK proprietary loader
<naobsd>
you can load your own code from mask rom mode with upgrade_tool/rkflashtool
<naobsd>
you can flash your own code with upgrade_tool/rkflashtool only if proprietary loader is running on target
<naobsd>
if non-proprietary loader is running, just follow regular way for that loader
<naobsd>
hmm I think "rkflashtool I" is better than "rkflashtool j" for writing idb...
<naobsd>
well
<naobsd>
everything should be overhauled ;)
zhecka has joined #linux-rockchip
zhecka has quit [Ping timeout: 252 seconds]
<akaizen>
enkoder: You can run system from microSD card and write mainline u-boot to eMMC and boot from that directly
<akaizen>
Ideally USB writing to eMMC would be great, second best is boot from network
<akaizen>
Does anyone have ChromeOS running on firefly or radxa?
<enkoder>
akaizen: I am trying to write my compiled version of u-boot to the emmc with `rkflashtool w 0xb800 1048576 < u-boot.bin` and am getting "rkflashtool: info: premature end-of-file reached."
<enkoder>
How would you write u-boot to emmc?
zhecka has joined #linux-rockchip
<akaizen>
boot system into linux with microSD card
<enkoder>
I see. Chicken and egg problem. Sounds like you cant do it from usb loader/bootloader