Cowon D2

[Yeeze]

Hey there!

I want to coda a little demo plugin...

To test it I want to use the D2 simulator...

I downloaded the already compiled one...

But when I just try to start any plugin (e.g. "fire") I get "The executable or DLL ...\fire.rock is not a valid windows executable..." (This message was in german my translation might not be perfect).
And in rock box the message "Can't open .../fire.rock" is displayed...

How can I run plugins in the simulator?

I also tried to run the simulator under cygwin, but rockbox said "Can't open .../fire.rock"


On the "Rockbox UI Simulator" page it says:

Goal

To enable Rockbox application and plugin developers to test and debug their code and concepts on a host PC as a complement to running on target.

So it should be possible right?

PS: Right now I try to compile a simulator myself... But I don't think that it will fix it...

[andiator]

I think, the first version should have key emulation only. There is still other stuff to be done.

But on the other hand...  

- The touchscreen support may not affect other non touchscreen targets, so we can only expand existing features.
- In settings there should be an option to switch between virtual keys and direct touchscreen support
- There should be a touchscreen (or mouse?) press/release event with x and y position
- The WPS have to be extended to have interactive tags reacting to events with (x, y) positions with corresponding actions, like stop, start and my favourite : choosing the position within the track. Then a backdrop with drawn buttons at right places - and we have a nice touchscreen support.
- For menu we need the position of the first visible item and the hight of one item.

The navigating in the menu is somewhat tricky. The items should be big enough to be used with fingers - a right theme will do.
Then the menu must be scrolled, for example with +/- buttons, select/open with M and back with power.
Tipp on the menu item would select it.

The simple gesture support would be very nice: moving finger down scrolls the menu down, the same for up direction: so the volume buttons are left for volume.
Moving finger to the right opens/selects the item, the left move is the back action.
Some plugin can have virtual keyboard...

Yeahh... that what I'm thinking/dreaming about at the moment

[Yeeze]

I already made a little brainstorming about a keyboard design....

The keyboard consists of buttons with each having multiple charcters on them. To type you push the button and drag your finge in the dirction of the key...

In my example to type 'a' this would be first button second row, toch and drag to the top left side...

To type delete (del) touchvery right button on bottom row and drag to top...

and so on, so you can have big buttons but still all keys on the screen

Here layout examples (5x3 keys):

Code: [Select]

Normal Layout:
|1 2|	|3 4|	|5 6|	|7 8|	|9 0|
|q w|	|e r|	|t y|	|u i|	|o p|

|a s|	|d f|	|g h|	|j k|	|l ß|
|z x|	|c v|	|b n|	|m æ|	|, .|

|caps|	| space bar |	|entr|	|del|
|spec|	| space bar |	|tab|	|backs|


Capslock:
|! ?|	|" '|	|§ $|	|& /|	|| ·|
|Q W|	|E R|	|T Y|	|U I|	|O P|

|A S|	|D F|	|G H|	|J K|	|L _|
|Z X|	|C V|	|B N|	|M Æ|	|; :|

|caps|	| space bar |	|entr|	|del|
|spec|	| space bar |	|tab|	|backs|


Special:
|1 2|	|3 4|	|5 6|	|7 8|	|9 0|
|( )|	|* /|	|% ^|	|+ -|	|= #|

|Ä Ö|	|Ü ×|	|{ }|	|[ ]|	|$ €|	
|ä ö|	|ü ÷|	|< >|	|« »|	|¥ Ħ|

|caps|	| space bar |	|entr|	|del|
|spec|	| space bar |	|tab|	|backs|


Capslock + Special
|¹ ²|   |³ ¼|	|½ ¬|   |Þ Ω|   |↑ →|
|@ ł|	|~ ¶|	|' `|	|þ §|	|← ↓|

|Ŋ °|	|© Ł|	|Ø ¦|	|“ ”|	|µ Ð|
|ŋ º|	|® ª|	|ø ĸ|	|‘ ’|	|ŧ ¢|

|caps|	| space bar |	|entr|	|del|
|spec|	| space bar |	|tab|	|backs|

It could be possible to create different layouts and save them, so every user can have a keyboard which fits their needs and expectations.

Put in code a we would have one button on a free definable x,y position, that can hold 'n' chars... Each char on this buttom has its ASCII value and an integer or float with one angle. This angle defines the dragging direction. In my scenario this would mean :
Example for button with "1, 2, q and w" on it:
Button positon: x,y
Char ASCII: '1' Angle 135°
Char ASCII: '2' Angle 45°
Char ASCII: 'q' Angle 225°
Char ASCII: 'w' Angle 315°

If you understand how I think of this....


But this can be discussed in more detail when the touchscreen is working right...

[andiator]

I've compiled the sim in vmware image - it does work. I could start the "invaders", I only forgott the button mappings  

[Yeeze]

Well the build is finished and it works too!

I dunno why the downloaded version did not work...

Thx andiator for the fast feedback!

[aidy]

I like the four on one keyboard idea, but i'd rather drag up down left and right instead of 45 degrees... I'm fairly sure it'll be much more natural?
could be wrong though
great to see lots of progress is made on the port, really can't wait to use rockbox on the d2!

[cybergrind]

how I can define state of LCD (pressen or notpressed)?

Maybe it generates interrupt? or we can get state in memory? I saw example in bootloader, but in it we read x,y state every cycle.

[shotofadds]

The 'touch' event comes as an interrupt from the PCF50606 chip (I believe it's signalled using the EXT3 IRQ, we then need to read the approproate data from the PCF interrupt registers). I'm still working on this, but I have other things on my mind at the moment....

[andiator]

For all who wants to test the current build:

On my ftp server (found in my signature) you can find bootloader.bin to patch your OF version, patched bootloaders for 3.54 and 3.55 (rename those to d2N.bin) and rockbox.zip.
For patching the bootloader see the wiki. http://www.rockbox.org/twiki/bin/view/Main/CowonD2Info
Don't blame me if something goes wrong, I tested it on my D2 8Gb OF 3.55 and had no problem.

[Yeeze]

Is there a way to only compile the plugin I'm currently working on? Espacially for the Simulator!

Because right now I'm running make and afterwards make install, and that takes quite long just to debug...

[Chronon]

I think you can use make rocks to only compile the plugins.

See here: http://www.rockbox.org/mail/archive/rockbox-dev-archive-2007-03/0039.shtml

I'm not sure how to only include just one plugin.  I guess you could just temporarily edit the SOURCES file?

[cybergrind]

shotofadds -> where we defines interrupt handlers? in system-tcc780x.c?

[shotofadds]

Interrupt handlers can be defined in any location, but ideally it should be inside a driver for the related functionality (eg. the ADC interrupt handler is implemented inside the ADC driver code).

Implement a function of type "void NAME(void)", whose name is one of those listed at the top of system-tcc780x.c (EXT0-3, ADC, etc). Assuming you have set the appropriate hardware enable bits (IEN, etc) it should be called automatically. See adc-tcc780x.c for an example.

On the D2 I think the EXT3 interrupt is used to signal events from the PCF50606, but this chip handles both power management and the touchscreen. Since the chip's primary purpose is power management, I think it's interrupt handler should be defined in power-cowond2.c.

I intend to do some work in this area at the weekend, hopefully we won't end up duplicating effort...

[cybergrind]

I read datasheet (something understand =) and test some functions. I could try to implement LCD and Battery driver (both or one of them - choose from you) at this weekend.
I think that NAND driver is more important now.

[gnu]

Is there a way to only compile the plugin I'm currently working on? Espacially for the Simulator!

Because right now I'm running make and afterwards make install, and that takes quite long just to debug...

I don't know how you can only complile one plugin, but you can skip the 'make install' when you write something like this:

Code: [Select]

cp apps/plugin/myplugin.rock archos/.rockbox/rocks/demos/myplugin.rock

With this code you only copy your plugin and not all the 'unchanged' pars of rockbox.