Rockbox Development > New Ports

Creative Zen Vision:M

<< < (93/136) > >>

mcuelenaere:

--- Quote from: Falafel on February 27, 2008, 08:23:13 AM ---When I compile and run (with finally the right dimensions on screen) I see the 7 hex codes I just added, with long (36 Bytes) never changing codes behind 'em, and the top one (0xE) has a constantly changing 4digit number behind the code.

Edit: the long ones are addresses? because they don't change.

--- End quote ---
Strange.
The format is as this: '0x[ADDRESS]: [READ 20-BYTES OUT ADDRESS]'.
If the long ones are FFFFFFFFFFF... or 00000000000... there isn't a slave device responding to that address.

But I conclude that the Zen Vision does have different hardware in comparison with the Creative Zen Vision:M.

BTW: what are the basepx and basepy values you use?

Falafel:
Basepx = 80;
Basepy =   0;

Well, maybe I could find the different information in the fresc of my zv?

Edit:
also, it was possible to run the Rescue program of the ZVM on the ZV so at least buttons and such should have the same interface I guess.. (Although I do not remember if I tried them..)

Edit2:
output on screen:
0xE: 00...00 FF...FF
0xF: 00...00 FF...FF
0x10E: 00...00 FF7FFBFF7FFBFF7FFBFF
0x10F: 00...00 FF...FF
0x1A2: 00...00 1BFF001841
0x1A3: 00...00 41119858080
ox20E 00...00 F7F7F7F7F7F7F7F7F7F7

mcuelenaere:
Whoow, I just see that I've got some new permissions on the forums  :)
Apparently, I got promoted to Developer? Whoever did that, thanks!  :D

Anyway, I'm getting close to the ATA driver, although I'm having trouble with ATA_CONTROL; I just can't seem to figure out which value it should have :S

As usual, diff is attached.

mcuelenaere:
I'm having difficulties with sleep() and more precise sleep_thread() (and maybe switch_thread() ), the device just restarts when some code calls sleep().
Were there any other ports behaving the same at this stage?
It seems like it has got to do with some ARM-specific code, as I don't think the (current used) DM320 code can reboot/crash the device.

As I see in the code, sleep() is replaced with a loop for some ports as they have problems with it at bootloader stage. But my problem is that actually bootloader stage is already passed; so it won't matter if Rockbox or the bootloader get loaded; both will have trouble with sleep()

Domonoky:
hi,

i seam to remember that on some targets the bootloader doesnt have the interrupts enabled, and thats why the replace the sleep with a loop.
Perhaps this also the problem here ?

good luck..

Navigation

[0] Message Index

[#] Next page

[*] Previous page