SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

[pbxy]

About the buttons perhaps modifying the button driver like the Clipv1 would help: read only 1 row at each tick, and prepare the next row to be read at the next tick. Can you look at it ?

That works fine for all the buttons except for hold.
Also, "View I/O ports" doesn't show a change of GPIOA when hold is active.

FM Radio: It even finds stations!

[funman]

About the buttons perhaps modifying the button driver like the Clipv1 would help: read only 1 row at each tick, and prepare the next row to be read at the next tick. Can you look at it ?

That works fine for all the buttons except for hold.
Also, "View I/O ports" doesn't show a change of GPIOA when hold is active.

Can you post a patch with your changes on flyspray ?

[pbxy]

Can you post a patch with your changes on flyspray ?

Here it is: FS#11111. Nice number!

[saratoga]

Can you post a patch with your changes on flyspray ?

Here it is: FS#11111. Nice number!

Is your name really Pascal Below?  If not, you need to fix that before your patch can go into SVN.

[pbxy]

Yes, that's my real name.

[saratoga]

Ok then that should be fine.

[funman]

I would like to make a new release of mkamsboot, which includes the fix for c200v2, and Clip+/Fuzev2 patching (even if those are still unusable at this moment).

That would also include the md5sums of OFs versions released since mkamsboot 1.1

Can someone test if Clipv2 OF v2.01.35 can be used without bricking your clipv2? md5sum of OF is a3cbbd22b9508d7f8a9a1a39acc342c2

[ranma]

I've polished my patch for software backlight brightness control and created a task on flyspray for it:
http://www.rockbox.org/tracker/task/11119
I also added my usb detect patch to the tracker:
http://www.rockbox.org/tracker/task/11120

Still pending:
c200v2 variant detection using gpioa7.
Waiting for feedback from bertrik (sent him an email with preliminary patch and compiled rockbox.sansa / english.lng).

For reference:
OF does variant detection by setting a7 to input and reading it back.
If 0 => my variant, a5 is buttonlight, a7 is backlight, d7 is 'menu' text light below power/menu button, no usb detect pin found so far
If 1 => other variant, a5 is backlight, d7 is buttonlight
OF (c200-03.02.05) has fiq handler for backlight pwm at 0x3d38, which reads the model variable from 0x202e9 (at 0x3d48) and backlight toggling at 0x3d8c (on) and 0x3da0 (off).
This variable is set by init_hardware(0x8000) subroutine, which also checks for another pullup/pulldown value on a1 on my model (usbdetect on other variant) and stores that at 0x202e8.

[edit]
OF VIC vectors:

Code: [Select]

> mdw phys 0xC6010100 0x10
0xc6010100: 00003d2c 00003bf4 00008e9c 00003d08 00003cfc 00003d14 00003d20 00003cf0
0xc6010120: 00000000 00003c5c 00003c74 00000000 00000000 00000000 00000000 00000000
> mdw phys 0xC6010200 0x10
0xc6010200: 00000021 00000024 00000023 0000002e 0000002d 00000025 00000027 0000002c
0xc6010220: 00000000 0000003d 0000003e 00000000 00000000 00000000 00000000 00000000

irq1 / timer1 => 0x3d2c
irq4 / dmac => 0x3bf4
irq3 / usb =>0x8e9c
irq14 / i2sout => 0x3d08
irq13 / i2sin => 0x3cfc
irq5 / nand => 0x3d14
irq7 / mci irq0 => 0x3d20
irq12 / i2caudio => 0x3cf0
irq29 / gpio a => 0x3c5c
irq30 / gpio b => 0x3c74

The gpio a handler checks for a6 and acks a6.
The gpio b handler is a bit more complicated, but it definitely acks b0.
[/edit]

[just_me]

@funman
> #define USB_PRODUCT_ID 0x74d1

Maybe add the USB ID for

Sansa Clip+ (mtp) or
Sansa Clip+ (msc)

to "The USB ID Repository"
https://usb-ids.gowdy.us/read/UD/0781/
as well?

Greetings,
Frieder

[funman]

the entry already present is for mtp (0x74d0), 0x74d1 is msc

I don't know how to edit entries, nor do i have a login so feel free to complete/correct this list

[just_me]

thanks, done.
(as a human operator checks it it will probably take a while until it really shows up)

[lazy]

I would like to make a new release of mkamsboot, which includes the fix for c200v2, and Clip+/Fuzev2 patching (even if those are still unusable at this moment).

That would also include the md5sums of OFs versions released since mkamsboot 1.1

Can someone test if Clipv2 OF v2.01.35 can be used without bricking your clipv2? md5sum of OF is a3cbbd22b9508d7f8a9a1a39acc342c2

does that fix the boot for the c200v2 that did not boot before

[funman]

includes the fix for c200v2

does that fix the boot for the c200v2 that did not boot before

Yes, i still want to wait until someone with a clipv2 test the last OF, so in the meantime you can build your own from svn

[FlynDice]

Just a little clip+ update.  If you haven't seen it by now, funman found the magic line to get sound!  I played music all day today with no problem whatsoever(with playback that is).  I am still working on writes to the SD cards with very little luck so far.

[mitk]

FlynDice, funman: Is this code in svn? I've flashed clip+8G with firmware made from svn r25276 and got ATA error. Is it consequence of differences between 2g and 8G clip+ or just I need to wait for your code in to svn?