Creative Zen Vision:M

[jonsey]

Problem!
After the uploading,and after the reboot i can see something on the screen...it says...
RockBox boot loader...
version r18405-080904
loading creative firmware


and after always the same original firmware 

[mcuelenaere]

So has the decryption error for the zen vision m 60gb rockbox.zvm60boot been fixed?

No(t yet).

As I'm not really into cryptography, this could be rather hard.
AFAICS, Blowfish in CBC mode only supports keys up to 56-bit (and this key is a bit larger).

@all:

Currently Rockbox is not yet available to users! All what the Rockbox bootloader does, is loading the _Original Firmware_!

Because of technical limitations (blame Creative!), we can't put Rockbox on the device (yet) without taking your hard drive out...

[jermey]

but im curious is this zvm port already functional i mean playing music. i dont care about glitchy buttons driver

[karashata]

Currently Rockbox is not yet available to users! All what the Rockbox bootloader does, is loading the _Original Firmware_!

I'd say that's a "No, it's not functional yet" if I've ever seen one.

[jermey]

I am just asking because long time ago i had rockbox running on my ZVM but there was no sound etc... just menus and very glitchy button driver which stopped my further testing (plugins etc.), so yes rockbox is not officially relased but there are experimental dev builds and my question is that builds are functional. I could check it by my self but its a lot of work to open my Zen connect hdd via ZIF<->USB connector, backup all data and then compile and put rockbox on it. So I would be glad if some developer (preferably mcuelenaere) said what the newest build can do.

[Llorean]

Frankly, if you're not going to be developing, you don't need to be posting in this thread. When there's a build that works, it'll move into "supported" and be on the front page of this site.

[clippey]

I can try to look into the blowfish decrypt problem, I have starting learning about cryptology, hopefully I can finally put it to some good use.

[mcuelenaere]

@all:
The status of the project hasn't changed since my last post (07-09-2008):

Rockbox is not available to end-users, but if you're really interested you can always try to install it; though it lacks all major DAP features (including no music playback).

The lack of understanding CFS is blocking an 'easy' installation of Rockbox, the lack of developers/developing efforts(including myself) is blocking the other parts of the port.

I'm not saying I'm not interested anymore, it's just that I'm not as motivated and having less Rockbox time available as I used to..

About the CFS problem: last time I talked to quetzalcoatl, he said he was close to fixing it; but as I haven't talked to him anymore I haven't looked into the issue anymore.

(More technical): AFAIK, the problem was that reconstructing files to clusters; so we could use the 'Virtual File System' (aka external disk drive/UMS mode) as a place to store our Rockbox FAT file system.
I believe all code is in SVN, or at least posted 'somewhere' online at the Rockbox site, and it's very close to working perfectly. (pointers: linky and linky)

Actually, we almost have all the pieces to fit the puzzle, just one or two are still missing to get the ZVM to at least boot Rockbox and possibly manouvre in it.

[Aurix Lexico]

Hello,

I know a bit of C I learned myself, mostly as a hobby. I just checked out the latest SVN, compiled the UI Simulator, and noticed that there are no plugins for the ZVM 30GB. Mcuelenaere asked for someone to try to add keymaps to the plugins back on page 38. Is the lack of plugins for the ZVM due to someone not spending some time adding keymaps for the plugins or some deeper problem? If it's the former, I wouldn't mind spending some time attempting to add the keymaps myself, I just need someone to point me in the right direction.

Thanks for all your work on porting rockbox to the ZVM.

[funman]

Hi

In most plugins you just have to define a keymap, and in some others you will need to set up screen sizes, perhaps edit some bitmaps, so you can definitely help by defining keymaps and testing plugins in the simulator.

Just enable plugins in the build (see tools/configure) and run make, edit the first plugin that breaks, run make again, etc ..

Hope that clears a bit

[mcuelenaere]

(Keep in mind that the keys currently aren't working on the device itself, so you won't be able to test the plugins (if you would get Rockbox installed that is))

[Aurix Lexico]

Whew, that took longer than I expected. All the plugins compile, and I was playing with a couple in the UI Simulator. Everything I tried worked ok. The keys are a bit inconsistent, I'll try to fix that when I have more time.

Link to my diff: http://www.mediafire.com/download.php?mio1mtczzxm

[LambdaCalculus]

Your patch is now on Flyspray, where it'll be safer.

See FS#9605.

(EDIT) Committed!

[Aurix Lexico]

(Keep in mind that the keys currently aren't working on the device itself, so you won't be able to test the plugins (if you would get Rockbox installed that is))

Just curious, but what would be required to get the buttons working?

[mcuelenaere]

(Keep in mind that the keys currently aren't working on the device itself, so you won't be able to test the plugins (if you would get Rockbox installed that is))

Just curious, but what would be required to get the buttons working?

Figuring out how the ZVM communicates with the PIC microcontroller (see the wiki for some information).

The buttons (and other stuff) is connected to a separate microcontroller, which 'talks' with the ZVM's main CPU over I²C. The problem is that we need to figure out what 'language' they're speaking..

I can receive button events from the PIC (ie when I press up, I get for example 0x20 as response), but the problem is these values can change when the OF has communicated with it; meaning the OF probably sets some kind of values in the PIC, which changes the responses that the PIC sents.