<Astralix>
I am actually rewriting rkflashtools and found lots of things we actually miss in the current version
<tonikasch>
ahmm
<kvirc_Guardian45>
somebody needs to just get after rockchip and explain to them exactly what the GPL means
<Astralix>
The problem with the current rkflashtool is, that it fails on large images like system.img. It completes but android fails
<kvirc_Guardian45>
sick of beating my head against the wall with broken source haf documented fuctions
<Astralix>
which documented function? I only see functions
<kvirc_Guardian45>
#define large
<kvirc_Guardian45>
iv flashed 900Mb images
<Astralix>
I have flashed many smalle images for kernel, recovery and boot, but it always fails on system.img
<Astralix>
400..600MB I guess
<kvirc_Guardian45>
bad usb plug ?
<kvirc_Guardian45>
force is mask mode do a complete whipe and try again I guss
<Astralix>
several USB plugs, different USB HUBs and different PCs (AMD and INTEL)
<kvirc_Guardian45>
odd
<kvirc_Guardian45>
defective NAND ?
<Astralix>
Stop guessing
<Astralix>
NAND is fine, and if I use rk windows tools, everything is fine
<Astralix>
But I do not have any windows
<Astralix>
and I don't like to start a VM with windows just for flashing
<Astralix>
while I develop and compile everything on linux I havt to have a windows VM running just for reliable flashing... that's not the way it should be
Topgun100 has joined #linux-rockchip
* kvirc_Guardian45
doesn't use linux enough to ./care
<kvirc_Guardian45>
rkflashkit-gui has never given me a issue but I haven't flashed anything larger then 600Mb with it
<kvirc_Guardian45>
iv done ~900Mb images in windows
<Astralix>
funny, same way of working, just different language
<kvirc_Guardian45>
I used it because it allows me to selectively erase partitions
<Astralix>
yes, my version does allow this too, now. I added the option to use R W E instead of r w e and then give partition name instad of address and size
<kvirc_Guardian45>
cool
<kvirc_Guardian45>
iv had weird issues with these mk908 sticks
* kvirc_Guardian45
should have bought a cx919
<Astralix>
I have no issue with 908, just hell of work on 802IV for WiFi and Bluetooth
<kvirc_Guardian45>
yea well I was unlucky enough to get a V3
<kvirc_Guardian45>
none of the current kernels sources work correctly
<kvirc_Guardian45>
they _all_ either dont boot or the cpu doesn't scale properly
<kvirc_Guardian45>
stock kerne works fine
<kvirc_Guardian45>
which is why I am a bit annoyed with rockchip because I don't have the sources so see what they are doing differn't on the V3 hardware
<kvirc_Guardian45>
and since I doing a debug kernel with current source seems like it would be a dead end because I don't know where to look
<kvirc_Guardian45>
and you can't really attach a kernel debugger to the stock kernel
<kvirc_Guardian45>
its perma-broken untill we get sources
* kvirc_Guardian45
isn't even really 100% sure if it was tronsmart the managed to break it or if rockchip did something to break it
<kvirc_Guardian45>
tronsmart just slaps a label on the side of it can calls it "theirs"
<kvirc_Guardian45>
I doubt it was there fault
<kvirc_Guardian45>
the older mk908 sticks ran hot the V3 was to fix that problem so something got broken someplace
<Astralix>
the 908 are pretty cheap trash. They don't have any DC/DC controller on them so you can't power-management in any way.
<tonikasch>
kvirc_Guardian45, the PMU chip for v3 mk908 seems to be an ACT8846
<kvirc_Guardian45>
yep
<kvirc_Guardian45>
but its noware on the PCB
<kvirc_Guardian45>
I mean NOWARE
<Astralix>
Telling it to power off results in LED is switched off and kernel goes to while(1)
<kvirc_Guardian45>
did they move it onto the soc ?
<Astralix>
There is no DC/DC controller, just fixed DC/DC switches
<Astralix>
nope
<kvirc_Guardian45>
so I should comment out the ACT846 and switch it to fixed
<kvirc_Guardian45>
I tried that once I think didn't make a differnt
<Astralix>
I guess I even did check if they use kind of PWM what they do with my 3066 in my tablet. But I cannot find any PWM on any of the DC/DC chips
<kvirc_Guardian45>
same thing here
<kvirc_Guardian45>
I am wondering if thats why the CPU scaling isn't working
<kvirc_Guardian45>
no PMU = no voltage register mapping
<Astralix>
yes, you have to limit the speed of CPU/GPU to stay within temperature range
<kvirc_Guardian45>
but it works in the stock kernel maby they have some voltage tables defined staticly
<kvirc_Guardian45>
I have 3 differnt V3 sticks
<kvirc_Guardian45>
all have the same issue two of them have cooling mods
<Legitsu>
that was one of the first things I tried
<Astralix>
How can I see if my 908 is a V3?
<Legitsu>
pop it open
<Legitsu>
and look
<Legitsu>
its writen on the pcb
<Legitsu>
if it works with omegamoons kernel
<Legitsu>
its not a v3
<Legitsu>
=/
<Legitsu>
omegamoons kernel just loops
<Legitsu>
same thing I get with the majority of other sources
<Legitsu>
no way to debug it
<Astralix>
V1.0
<Legitsu>
:(
<Legitsu>
id be happy with the stock kernel but its slow
AstralixNB1 has quit [Quit: Leaving.]
<Legitsu>
and has issues playing video
<Astralix>
I can reproduce that thing on Android with some video formats
<Astralix>
If I use stock image, old or new, It plays youtube flawless.
<Astralix>
If I use image built from R-BOX sources, I have video issues on Android
<Astralix>
I switch to MK802IV which looks like some better piece of hardware
<Astralix>
Little bit more space, cooling plate, DC/DC converter and interesting software bugs
<tonikasch>
what about a Minix X7? I have bought that instead of a MK888B
<tonikasch>
haha, interesting software bugs
<Legitsu>
meh
<Legitsu>
I don't have anouther 80 bucks to spend on a device
<Legitsu>
that MAY or may not work
<Astralix>
I am not really interested in these things for using them as mediaplayer or such. I disassemble them and build drivers, create missing sources from disassembly or such things.
<Legitsu>
that was part of why I got it
<Astralix>
Some mainline kernel porting of 3066 and 3188
<Legitsu>
but whats the point of doing it if they can't be made todo something usefull
<Legitsu>
there nice little "toys"
<Astralix>
It is for understanding, learning, doing funny things and may be they will end on the TVs in my child's rooms
<Astralix>
I am waiting for an X9 or such that has WiFi, LAN and SATA or USB 3.0 and at least 4 ports of it
<tonikasch>
mmm, SATA!!?? :D
<Astralix>
Yep, make it a media base station that is able to serve and convert stream formats
<Astralix>
I'd like to hook... lets say 4 SAT sticks and a RAID5 of several 1TB HDDs to it
<tonikasch>
:D
<Astralix>
Unfortunately it will end in some chinese company making nice case, having 2 SATA and 4 USB 3.0 routet out but put all of them to a single 500mA DC/DC and the media converter cannot convert 2 SAT streams for use by tablet as it has to stay 1/4 of it's highest speed as there is only a fixed regulator of the core voltage and the core is overheating ...
<tonikasch>
:s
<Astralix>
Let's see what RK32xx will bring. But a SATA or two USB3.0 would really be fine.
<tonikasch>
that would be more than fine :)
<tonikasch>
well, have to go to bed, see you later
<Astralix>
In the RK Presentation no facts for USB / SATA are mentioned. But as they tell about 4k decoding they need an interface that can get the data into the decoders fast enough
<Astralix>
Same with me. Have business travel tomorrow
akaizen_ has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
Theueip_ has quit [Quit: Leaving...]
Legitsu has quit [Remote host closed the connection]
<naobsd>
Astralix: 0x00061B00 should be something like cpu/chip id
<naobsd>
you can find same values (different byte order) in arch/arm/plat-rk/include/plat/cpu.h
<naobsd>
0x00061a00 is used to get nand info (currently I only know about 3 bytes)
<naobsd>
0x000a0300 is used to get bad block info
<naobsd>
0x000a0600 can be used to erase IDB, but I don't know how to calc proper CRC block which is written by 0x000a0500
<naobsd>
0x000a0b00 is used to erase nand (physical addressing)
<naobsd>
device descriptor bcdUSB can be used to check mask rom mode
<naobsd>
rkflashtool erase was implemented by original author long time ago, I have no idea why it was missed ;)
<naobsd>
(rkflastool erase == just writing 0xff, not real erase)
MrWHO has joined #linux-rockchip
<MrWHO>
Hi - I am trying to figure out something: I have XBMC compiled with cedarx accelleration, but if I try and play a 720p h264 media it looks very "choppy" - I know it's doing hw decoding, software only is basically a slideshow. I'm using the android libvecore to avoid issues with some media. I'm on a h24 .
<MrWHO>
On the same device mxplayer under android plays with HW decoding the same media without any issue.
<MrWHO>
What is my best option at the moment to run XBMC and see at least 720p without glitches?
<naobsd>
MrWHO: here is linux-rockchip, not linux-sunxi