Hooray!!! Rockchip SDK!

[flasher86]

I had already killed my player once, and I had to disassemble to case and manipulate with pins on the chip to reset it, but It worked.

Also, I have a dozen of working firmwares. My original firmware didn't even support RKP platform, but after searching for other firmwares (and from other players) I got support for RKP, FLV, APE and FLAC where these were unsupported by default.

I have on mind something to get the screen work. Of course the source is designed for 220x176 screen but If I manage to display it on my 320x240 then, the doors are open for any design modifications.

I will try to read out memory using RKP file (I copied ReadMem32 and ReadMem from the SDK and it works on RKP platform) to find out how to initialize screen, and perhaps it will allow me to just copy the memory and get the screen work. Those functions really work with my firmware from. I am able to control contrast from RKP file, to turn off the player, turn off lcd and turn it on again. Its even better, the contrast control allow to get smooth slide from dark to high contrast, not just 6 levels, but 10 000 levels instead.

If that will work, I will make a diagnostic RKP file for anyone, and any non branded player.

To not kill my player this time, I will modify the source the way that it will go into usb firmware upgrade mode without holding any button. Because buttons may also be confused.

Huge thanks for your help.

edit:
The build you send me builds and creates .out file but its weird that there are so many warnings. Not only during compilation but also during linking with some memory regions. Have you got the same? Does it work despite all those warning messages? It so, its a shame that Rockchip made such a dirty source code for commercial purposes.

edit2:
I uploaded compiled firmware into my player, but it doesn't boot up properly, black screen. But the good news is that the code is executed. I changed the source in a way that it gets into USB Rock Device just after plugin it into the PC, without pressing anything. So what ever happens, i have access to upgrade mode.

[knob]

Yes it works fine on my player in spite of the dirty code.
Did you set the screen size up in lcd.h ?

#define LCD_MAX_YSIZE 176
#define LCD_MAX_XSIZE 220
#define DATA_BUS_WIDTH 16

Also I managed to create the black screen in LCD_NEW_M_205.c
I put some comments in.

My flash type is MLC,
[NAND FLASH TYPE]
FlashType=MLC_2K in RK2606_MLC_Player.ini would yours be the same too?

[flasher86]

I think it is the same. I ve been looking for info which memory type I have and on some chinese websites it was said that it is MLC but dont know whether it is MLC_2k or MLC_4k (whats the difference?). Of course I'm not 100% sure about this, because translators are awful especially with chinesse.

I ve been looking through your LCD_NEW_M_205.c file and you ve done nice job there. But this file is not added to the project. You use it instead of lcd.c? or it is linked somewhere in code?

I havent changed anything to lcd, but I think the prior is to init lcd on, as the backlight doesnt even turn on. I am just experimenting, and dont know whether it will work anyway with my touchbuttons.

I have Teclast C260-CI (its actually polish rebranded version called Pentagram Vanquish R Touch). Here is photo.

[knob]

It's linked in Macro.h , lots of other parameters are in there too.
You will see 1 or 2 other comments by me in Macro.h.

It was the driver that worked best for me, but there are some other display drivers.

btw
My flash memory is 2GB I tried a SLC memory type by mistake and I got the bad block problem, very hard to recover from. If yours is memory MLC then safer to stay with MLC.

[flasher86]

maybe I will create some loop in which all the drivers are get initialized in every 1 minute, so it would be tested at once. If none of these drivers don't work, the last option is my previous idea to read out memory using rkp program. I noticed that most lcd drivers write data to the very first regions of memory, so it shouldnt take too long for writing down (on paper) values from memory displayed on screen.

One more thing, did you shortened this firmware source code? Because I noticed it lacks of many features like LRC or AVI, or did you find that one just as it is?

[knob]

Yes, I stripped loads of stuff out, I wanted to make a minimal firmware. It can browse files, display .jpgs and play mp3s. It has a new character set and scrolling text. It would be easy to restore if needed, but it just has tetris game, no .rkp loading.

If you find you can use this firmware the original download is here:-
http://ftp.zsctc.com/RK2606A_SDK_1.08_Release.rar
password ttee

[zengfeng1897]

RK26xx and RK27XX are very different.
RK26xx needs a special compiler, and RK27xx needs the tool for arm (ADS).
Do not try any firmware on your player, the differen is not just about the LCD driver , some time the nand flash driver will also be a problem.
and the hardware design will also cause you some trouble.

[flasher86]

Currently I abondoned preparing firmware for my player. It causes too many problems, the firmware executes and enables upgrade mode but non of the devices are working properly.

look at this thread:

Google Tłumacz

the only thing which pushed me into own firmware is the support of opening external files. But in this thread SWIRL is saying that it can be done in RKP file, so if it works, there is no need to do this.

Also I ve been working on RKP platform and I am pretty close to MP3 support INSIDE RKP file, so I will be able to make my own mp3 player with AlbumArt support, spectrum analyzer and much more just by using RKP file.

The funny thing about original firmware is a huge loss of performence because of lazyness of programmers. The original firmware works in a way that graphics are displayed directly from flash data, so everytime something needs to be displayed, it looses a lot of time to read from flash.

What I noticed is that when the graphics are preloaded into SDRam the performence of displaying graphics raises up to 10x faster. Spectrum analyzer will work like a charm, and everything should work a lot of faster even during mp3 playback.

[knob]

Yes I agree, if we can open a file from .rkp then it's just drag and drop upgrades and no need to worry about screen drivers and memory types.

I have another Rk2608 player that loads in .rkp games too, but I didn't mess with the firmware on this player because I don't have a backup and I don't want the lose the .rkp platform.

If a music player can be made from a .rkp then more users could test it out safely too.

We could always look at making a simple configurable .rkp loader for rk26xx players that don't support games later.

[knob]

Just managed to compile the RK27 SDK fully.
Copied it over to my player, this one:

And guess what it worked! I can play music and navigate with the buttons and the FM radio works too!

Just one snag however, the display was white, but I have got a fully working firmware (apart from the display).

I have just started looking at the screen drivers to see about giving them a tweak like I did for the RK2606 firmware.
This firmware seem quite up to date, just looked at the source and it features album art and nes emulation.
If I get further success I will post some photos.