ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
bludot has quit [Quit: Connection closed for inactivity]
kapouer has quit [Quit: kapouer]
premoboss has joined #linux-rockchip
Ueno_Otoko has joined #linux-rockchip
naobsd has joined #linux-rockchip
nighty^ has joined #linux-rockchip
daniels has quit [Ping timeout: 240 seconds]
nighty^ has quit [Ping timeout: 240 seconds]
daniels has joined #linux-rockchip
hipboi has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
afaerber has quit [Ping timeout: 240 seconds]
Ueno_Otoko has quit [Ping timeout: 240 seconds]
afaerber has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
hipboi_ has joined #linux-rockchip
hipboi has quit [Ping timeout: 240 seconds]
<naobsd> oh
bludot has joined #linux-rockchip
<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.
<hipboi> not updated for a while
<aborche> hipboi, this kernel is not build correctly
<aborche> :(
<Omegamoon> aborche, tried the rk3128 as an alternative for the rk3188?
<aborche> hipboi, your wiki is my handbook every day. very good resource
<aborche> Omegamoon, i'm end user who use tv sticks for some interesting projects.
<Omegamoon> rk3128 at least has 3.10 kernel with all features working
<aborche> Omegamoon, and when someone ask me "do you have hardware video acceleration ?", my answer is "no, only in development'
<Omegamoon> what are you using, Linux or Android?
nighty^ has quit [Quit: Disappears in a puff of smoke]
<aborche> Omegamoon, radxa kernel 3.0.36+ - first kernel which started without any problem(only wrong voltage at wifi chip) at my board
<hipboi> aborche, check mac-l1's libhybis implementation
<aborche> Omegamoon, i need linux.
<aborche> hipboi, mac-l1 is worked ok. but ...
<aborche> i need hardware acceleration in chrome or nwjs. old kernel mali modules work, but chrome cannot use all features. only accelerated flash.
<aborche> fbturbo and sunxi fbdev is not a good choice
<hipboi> aborche, switch to rk3288 :)
<aborche> heh :)
<aborche> too expensive for development :(
<aborche> and for mass use
<aborche> also last ugoos linux firmware for 3288 based on 3.10 kernel
<hipboi> aborche, maybe not as expensive as you thought
<aborche> this is very strange
<aborche> hipboi, may be. but price 40$ for 3188 and 120$ for a stick with 3288 is too much
<aborche> and delivery, support, warranty is not included
hipboi has quit [Ping timeout: 256 seconds]
hipboi has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
<aborche> ok. what about mk903V ? price in moscow = 9000 rub ~ 128$ :(
hipboi has joined #linux-rockchip
<aborche> or rkm v5.
<aborche> good choice or no ? rkm only in pvc case, mk903v - alumunium
ckeepax has quit [Ping timeout: 256 seconds]
<vickycq> aborche: what about buying on aliexpress, mk903v can be bought for ~80USD
hipboi has quit [Read error: Connection reset by peer]
<aborche> too many clones :( my cx-919 which i purchased in moscow, was a fake
<aborche> mk809 with rk3188t
hipboi has joined #linux-rockchip
<aborche> and delivery from aliexpress to russia takes from 15 to 45 days
<aborche> from china ofcourse
maz__ has left #linux-rockchip ["Leaving"]
maz__ has joined #linux-rockchip
steev has quit [Ping timeout: 260 seconds]
steev has joined #linux-rockchip
steev has quit [Ping timeout: 256 seconds]
<aborche> hipboi, tell me please. if i'm edit radxa-rock2-square-box dts file for rk3188 pinout, this can be run at current square-box kernel ?
steev has joined #linux-rockchip
<aborche> this -> it :)
<hipboi> aborche, no
steev has quit [Ping timeout: 255 seconds]
<aborche> why ?
<aborche> ofcourse with correct voltages and frequency
steev has joined #linux-rockchip
steev has quit []
steev has joined #linux-rockchip
Astralix has joined #linux-rockchip
pietrushnic has joined #linux-rockchip
hipboi has quit [Read error: Connection reset by peer]
hipboi has joined #linux-rockchip
vickycq has quit [Quit: WeeChat 1.0.1]
hipboi has quit [Quit: Leaving]
<aborche> hm. why repo "wip/lsk-android-14.04-radxa-rock" deleted everywhere ?
cnxsoft has quit [Quit: cnxsoft]
nighty^ has joined #linux-rockchip
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
<akaizen> Yea :/
<enkoder> bummer
<akaizen> as long as you can dd to eMMC you're OK
<akaizen> you have SPL and uboot?
<akaizen> flash SPL: sudo dd if=out of=/dev/mmcblk0 seek=64
<akaizen> Flash u-boot: sudo dd if=firefly/u-boot-dtb.img of=/dev/mmcblk seek=256
<akaizen> short of reverse engineering USB protocol, network boot will be fastest or pre-made microSD
<enkoder> hmm ok
<zhecka> about what speech ? :)
<enkoder> speech?
<zhecka> talk :)
<zhecka> discuss :)
<enkoder> Yeah like us gibber-gabbing now, shootin the shit, little chit-chat. What about it? :)
<naobsd> I said "rkflashtool j" does it (if proprietary loader is running)
<naobsd> "rkflashtool w" is not for it.
<enkoder> I'm still getting premature end-of-file. Do I need to do any post processing on the file? rkcrc?
<naobsd> rkflashtool say so if you specified such arguments
<naobsd> I don't know it's wrong or not wrong
<naobsd> it depends what you're doing
<naobsd> you need to understand what you're doing
<zhecka> hm. i dont' understand, why nobody can't decompile code and make an open source fork
<enkoder> Good call naobsd, I dont know what im doing yet :)
<naobsd> enkoder: it's easy to use dd on running system, I recommend it. what rkflashtool can do is another story
<enkoder> ok I'll start with a working method first
jas-hacks has joined #linux-rockchip
<naobsd> probably it will be possible that load/run u-boot from OTG, then flash spl/u-boot from u-boot with SD/USB/TFTP/etc
<naobsd> in future
<sjoerd> Upsream should hopefully be able to do that after the holiday season :P
<sjoerd> on rk3288 thatis
<naobsd> :)
<enkoder> that would be EPIC!
<sjoerd> Figuring out why a u-boot loaded over OTG can't boot a linux kernel atm is high up on my spare time hacking list for the holidays
<sjoerd> once that's there a lot of possibilities open up
<naobsd> ah I remembered about dwc2 device mode and fastboot
<sjoerd> yeah the rockchip guyswere hacking on that part
<sjoerd> for 3036 iirc
<sjoerd> Which would be great as then you could indeed load things to eMMC from u-boot using stnadard u-boot stuff
<akaizen> being able to flash multiple boards from network/usb would be a godsend in terms of automated testing
<akaizen> let me know if I can help / you have a repo up
<sjoerd> yeah, kernelci is booting my rockchip board over the networkwith my u-boot which is pretty cool
<naobsd> I have interest about kylin board
<naobsd> RK people is working very actively
c0d3z3r0 has quit [Excess Flood]
c0d3z3r0 has joined #linux-rockchip
<enkoder> sjoerd: kernelci looks awesome. Thanks for pointing that out.
<zhecka> guys, which version of cross compiler you use for build kernels ?
cosm has joined #linux-rockchip
<naobsd> which kernel?
<naobsd> I'm using gcc 5.3 for mainline
<naobsd> using prebuilt gcc in Android SDK for kernel in Android SDK
<naobsd> zzz
<zhecka> for 3.10 and 3.18
<akaizen> sjoerd: ooo kernelci got netboot working with your branch?
<akaizen> do you have details?
<sjoerd> akaizen: though rperier mentioned he didn't get it working on the firefly, while it does work on rock 2
premoboss has joined #linux-rockchip
<akaizen> sjoerd: thanks. do you run your own local kernelci or link up with kernelci.org ?
<sjoerd> akaizen: Collabora runs it's on lava lab, kernelci.org uses our lab amongst others
<zhecka> sjoerd: why you do not share info about your cool projects on linux-rockchip.org ? all info on this site is very very old.
<sjoerd> zhecka: Because i prefer to spent my little time pushing patches to the various upstreams :)
<zhecka> naobsd: which version of armeabihf cross compile toolchain recommended for 3.10 and 3.18 kernels ? or last is fine too ?
<zhecka> sjoerd: hehe :)
<zhecka> shit :( default radxa kernel config doesn't build at rock2-square kernel source ;(
paterw00t has joined #linux-rockchip
c0d3z3r0 has quit [Excess Flood]
c0d3z3r0 has joined #linux-rockchip
Omegamoon has left #linux-rockchip [#linux-rockchip]
jas-hacks has left #linux-rockchip [#linux-rockchip]
gb_master has joined #linux-rockchip
gb_master has quit [Quit: Leaving]
zhecka has quit [Quit: Page closed]
Wizzup has quit [Ping timeout: 246 seconds]
Wizzup has joined #linux-rockchip
cosm has quit [Quit: Leaving]
<naobsd> zhecka: for 3.10 i.e. RK Android SDK kernel, use default prebuilt gcc i.e. don't define CROSS_COMPILE (see Makefile)
naobsd has quit [Quit: naobsd]
paterw00t has quit [Quit: Leaving]
enkoder has quit [Ping timeout: 256 seconds]
enkoder has joined #linux-rockchip