Creative Zen Vision:M

[Falafel]

Yeah, you'r right..
Hmm, too bad.. Ah well, maybe I should learn how to write USB-drivers :s

Edit:
Correcting the fact that some words might sound the same, but look quite different in writing..

[DanielF50]

just what would be required to get rb working on the zvm with a cfs partition?

Understanding of the CFS file system (I believe it is based on BFS; quetzalcoatl on nomadness.net found out a lot of interesting stuff and he even made a fully working read-only driver for the first (minifs) partition, but unfortunately the site is now online and most of his information on the forums is lost (except in google cache, archive.org) + there seems to be no way of contacting/finding this person

I tried contacting the website owner, but failed. I also contacted a guy who he spoke with on the forums (and who is a main developer at libnjb), but he doesn't have any contacting information.

http://www.whois.net/whois_new.cgi?d=nomadness&tld=net

Email, Address, Name etc all on there, hopefully he still uses those details.

Daniel

[mophead740]

I'm just wondering, if i wanted to get to work on my own usn driver, how would I go about it?
What kind of programming skill would it take?

Setting up the build environment should be no problem for me its just the coding that I'm wondering about.

EDIT:

I was looking around at the documentation for the usb chip and found this pdf that explains how to program it for windows ce 5.0.


has anyone else read it becauase it seems to me that its exactly what we need.

it even explains the way the chip handles interupts and the commands to use etc so it could be just what we need.

i think its based in c++ though, which could be a problem but most of it I'm sure is modifiable.

you can find it here http://www.nxp.com/acrobat/applicationnotes/AN10052_1.pdf

EDIT 2:

probably the most interesting part goes somewhere along these lines

Code: [Select]

The ISP176x can handle interrupts, such as SOF, ATL, INTL and ISO.
A separate thread, UsbInterruptThreadStub () in Chw.cpp, is run to handle these interrupts.
Whenever there is an interrupt to the ISP176x, interrupt thread UsbInterruptThreadStub () will be called.
This main interrupt handler handles all the ISP176x generated interrupts and routes interrupts to the respective interrupt handlers.
For example, PhISP176XScheduleATLThread () handles ATL interrupts and PhISP176XScheduleINTLThread () handles INTL interrupts.
If, for example, you are working on ATL, you will get an interrupt only when PTDs in the ATL memory are done.
If you are working on INTL, you will get the interrupt only when PTDs in the INTL memory are done.
Remark: The ISP176x Windows CE software stack is tested on the PCI bus for the x86 processor.
© Koninklijke Philips Electronics N.V. 2005. All rights reserved.
Application note Rev. 01 — 27 October 2005 16 of 173
Philips Semiconductors AN10052
ISP176x Windows CE 5.0 Software Programming Reference
The PCI interrupt is routed to the ISP176x interrupt through the PLX9054 bridge.
If porting to other hardware platforms, add interrupt number MemBase and MemLen in P1761HCPDD.reg.
For example:
For interrupt number:
SysIntr = dword: XX /* XX indicates interrupt number */
For memory base address:
MemBase = dword: XX /* XX indicates memory base address */
For memory length:
MemLen = dword: XX /* XX indicates memory access length */
If you are working on other hardware platforms, ignore the PLX bridge initializations in system.c.
edit by mcuelenaere:
made your post a bit smaller

[mcuelenaere]

http://www.whois.net/whois_new.cgi?d=nomadness&tld=net

Email, Address, Name etc all on there, hopefully he still uses those details.

Daniel

Yes, I already tried contacting this person but he didn't respond.

Yeah, you'r right..
Hmm, too bad.. Ah well, maybe I should learn how to write USB-drivers :s

I'm just wondering, if i wanted to get to work on my own usn driver, how would I go about it?
What kind of programming skill would it take?

Setting up the build environment should be no problem for me its just the coding that I'm wondering about.

The only skill you'd need is C (and perhaps assembly reading, if you want to know how the OF does the USB) + you need to understand a bit how USB works (see url) + the datasheet.

At the moment the only working thing is you can receive a EP0SETUP package but that's it.

Keep in mind the interrupts aren't really working for some reason, so I've created a helper (tick task) which checks the interrupt register of the ISP1583 regularly and calls the interrupt handler if necessary.

The ISP1583 registers are accessed in 16-bit mode, so an int has to be set in 2 clock cycles (see the set_int(...) macro)

That's about it, I recommend using the bootloader build as this gives you the advantage of doing printf's while normal build only supports logf (which means less trial-and-error productivity ).

PS: the files you're interested in are

• firmware/drivers/isp1583.c
• firmware/export/isp1583.h
• firmware/target/arm/tms320dm320/creative-zvm/usb-creativezvm.c
• firmware/target/arm/tms320dm320/creative-zvm/usb-target.h

edit:
There is some example source available at NXP (you'll need an my NXP account to log in)

[Falafel]

@mceulenaere
Hmm, when I try to compile it gives me an error that probably hinges on: "error: dsp-image.h: no such file or directory"

When I did a quick search I found that the Mrobe500 folks found the same problem, and although you gave a new patch the problem remains..

Edit:
Also, when I merge your diff with my source tree, it complains about audio-creativezvm.c not having an URL and then won't allow me to do anything.. Is this to be expected or should I stop using tortoise-SVN :p

[mcuelenaere]

@mceulenaere
Hmm, when I try to compile it gives me an error that probably hinges on: "error: dsp-image.h: no such file or directory"

When I did a quick search I found that the Mrobe500 folks found the same problem, and although you gave a new patch the problem remains..

Edit:
Also, when I merge your diff with my source tree, it complains about audio-creativezvm.c not having an URL and then won't allow me to do anything.. Is this to be expected or should I stop using tortoise-SVN :p

The bootloader isn't committed to SVN, but here's a patch for it (apply it to a clean SVN).

P.S.: you'll need to "#define logf printf" in isp1583.c otherwise debug won't show up..

[Falafel]

Ah, well it seems ZVM has finally crossed a border where my lowly ZV couldn't follow. As it is, it compiles quite fine, it gets loaded to my player without questions. But when it resets it just complains about firmware error..

So now I'll have to find out what broke compatibility, before I can even start on the USB. (Or I'm forgetting something crucial, since it's been awhile ago that I last tinkered with it.. But I cannot remember an error like this. So I guess not..)

[mcuelenaere]

Ah, well it seems ZVM has finally crossed a border where my lowly ZV couldn't follow. As it is, it compiles quite fine, it gets loaded to my player without questions. But when it resets it just complains about firmware error..

So now I'll have to find out what broke compatibility, before I can even start on the USB. (Or I'm forgetting something crucial, since it's been awhile ago that I last tinkered with it.. But I cannot remember an error like this. So I guess not..)

What exact message does it give you?

The only possible think I can think of, is that the flash bootloader finds an incorrect firmware which did get passed through the firmware upgrade..

Could you send me "rockbox.zvm"/"rockbox.zvmboot" ?

[Falafel]

The error it gives is: "firmware problem" AKA it's the rescue system (coming to the rescue?).

O!

You already construct a complete firmware!
Haha, that should solve it.

Edit:
To clearify: I used creative wizard to make a new firmware, while this was (obviously) not neccesary..

[mcuelenaere]

The error it gives is: "firmware problem" AKA it's the rescue system (coming to the rescue?).

O!

You already construct a complete firmware!
Haha, that should solve it.

Edit:
To clearify: I used creative wizard to make a new firmware, while this was (obviously) not neccesary..

Yes, in current SVN you don't need to do anything more except just sending it to the player

[Falafel]

here is the diff you need to get the keys working well on a ZV
http://rapidshare.com/files/114474489/zv.diff.html

Also, beware that the bootloader file that is created is still faulty, at least for me it is.. so if anyone wants to test it they should first open it in creative wizard or something and check if the codes and device names are correct.

[mcuelenaere]

As some may've noticed, a simulator for the ZVM (60GB) was submitted some days ago.
If someone feels to it, he/she can compile SVN and try adding keymaps for the plugins and post your patch here or at Flyspray.

If it complies with the Rockbox rules (i.e. use 4 spaces instead of tabbing etc), it will be committed to SVN.

[jermey]

I noticed there is flash memory dump in wiki so if you could read flash memory could we also write something to it? I'm asking because i have broken zen that isn't switching on when hdd is plugged in. I see only creative logo then black screen and reset. I have 1,8"->usb adapter so if somebody could help me i will be pleased.

[mophead740]

where did u get that 1.8 to usb adaptor?

i didnt realise you could get it like that.

that sounds good.

[jermey]

I just bought hdd 1,8" external case with ZIF connector inside and thats all. If it useful I can help with some Rockbox porting things. I found something interesting. When i plug this adapter to this "zen connecting thing" instead of hdd and plug it to computer and then switch zen on its switching on but nothing happens. Screen is black but led is on (not blinking) and led which is on this adapter is sometimes blinking like zen was trying to write or read something from hdd. Maybe somebody will find it useful.