Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Thank You for your continued support and contributions!

+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
« previous next »
  • Print
Pages: 1 ... 79 80 [81] 82 83 ... 129

Author Topic: SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2  (Read 1337495 times)

Offline funman

  • Developer
  • Member
  • *
  • Posts: 645
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1200 on: October 16, 2009, 10:59:34 AM »
server adds crlf to .txt files ..
* rockbox.sansa.bz2.1.bin (128 kB - downloaded 173 times.)
* rockbox.sansa.bz2.2.bin (122.23 kB - downloaded 200 times.)
Logged
a wise man said: "a wise man said"

Offline LiquidAcid

  • Member
  • *
  • Posts: 5
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1201 on: October 16, 2009, 11:03:24 AM »
Nope, doesn't work for me. Displays still turns white once the bootloader is through. Again tested both with and without the microSD card.

EDIT: Just logged into IRC, same nick as here. In case you want me to test some more without spamming the board.
« Last Edit: October 16, 2009, 11:07:54 AM by LiquidAcid »
Logged

Offline epithetless

  • Member
  • *
  • Posts: 195
    • Dour Times
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1202 on: October 16, 2009, 11:34:40 AM »
With the thought that this may not yet be known and may aid in development:

I am able to bypass the whitescreen on my 8GB Fuze v1 once it appears by repeatedly pressing the Play button. The time (and number of presses) it takes varies. The menu then displays normally. However, there is tremendous lag in player response time after this point, to the degree that it makes operation unfeasible. I don't know if this behavior is merely a result of the distressed loading process, but perhaps someone with more coding savvy will find the information useful...


[I've edited the above post to provide more detail. The procedure (repeatedly-pressing-Play-to-bypass-the-whitescreen) seemed more effective with r23199 than with the most recent build (r23203), but it still works after a fair amount of button pressing.]
« Last Edit: October 16, 2009, 12:54:58 PM by epithetless »
Logged
Rockboxed: Apple iPod 3G â€¢ Apple iPod nano 2G • iriver H120 • Sansa c250 v1 • Sansa Clip v1 • Sansa Clip v2 • Sansa Clip+ • Sansa e280 v1 • Sansa e280v2 • Sansa Fuze v1  |  non-Rockboxed: HTC Incredible [Android 2.2] • Sansa Fuze v2

Offline LiquidAcid

  • Member
  • *
  • Posts: 5
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1203 on: October 16, 2009, 11:37:45 AM »
At what point exactly do you press play? Does it matter how long the whitescreen is already displayed?

I'm asking because I can't seem to reproduce this. Pressing play doesn't give me the normal menu screen on my Fuze v1.
Logged

Offline FlynDice

  • Developer
  • Member
  • *
  • Posts: 166
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1204 on: October 16, 2009, 12:38:47 PM »
@ Those with fuzes getting white screens:

Would you please try changing line 369 in system-as3525.c from CVDD_1_10 to CVDD_1_20.
  This keeps the voltage scaling code in place we just don't lower the voltage to 1.10 volts, it "changes" it to 1.20v where it already is.

If this solves the white screen would you then try going back to CVDD_1_10 and then comment out line 342:
        while(adc_read(ADC_CVDD) < 480)
  This is the check that the voltage has returned to 1.20 before we boost the frequency.

If that works uncomment and I would be interested if changing the value from 480 to either 470 or 460 works.
  This cheats down just a little bit from the 1.20V we're looking for.

Thanks!

EDIT:
I've lowered the voltage check to 1.175 volts and it seems to do the trick.
Thanks liquidAcid for all the testing!
« Last Edit: October 16, 2009, 01:48:51 PM by FlynDice »
Logged
e280v2    fuzev1 2gb   clip+4gb   8GB Transcend cl6 uSD    access to fuzev2 4GB       clip+2gb R.I.P.

Offline kugel.

  • Developer
  • Member
  • *
  • Posts: 271
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1205 on: October 16, 2009, 02:58:39 PM »
Quote from: funman on October 16, 2009, 10:51:18 AM
Quote from: kugel. on October 16, 2009, 10:48:23 AM
I was wondering how this is possible if we use the same setting as the OF.

Are you sure the OF use 1.10V ?

That was according to you. Use looked at the disassembly and told that :)
Logged
 

Offline FlynDice

  • Developer
  • Member
  • *
  • Posts: 166
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1206 on: October 19, 2009, 12:02:22 PM »
I think I've figured out the CLKIDE link.  I think CLKIDE is MCLK for the pl180 controller for the internal SD.  I ran test_disk on the internal SD with IDECLK at 82 MHz, 62MHz, and 24 MHz and I think the results point strongly to this conclusion.  See the attached file.

I'm not looking for agreement here, I'm looking for reasons to disprove this hypothesis!
Fire away.


Edit:
Assuming this is correct I have been able to run the internal at 24.8 MHz and it works fine but feels a bit sluggish.  Once again I cannot run data without the bypass bit set so I can't run the controller MCLK at 49.6 and divide by 2 to get MCICLK = 24.8 MHz. I have to run the controller at 24.8 MHz and that slows things down...

Another thought is that we are overclocking the internal card much more than we thought.  The internal card is a v1(I tested on my e280v2 and I'm assuming the same for the rest of the as3525's) and , in fact will not accept the switch to HS timings. Which means the spec frequency is 25 MHz max.  We're currently running at 82 MHz MCLK with bypass meaning the card is being clocked at over 3 x the maximum!!
* IntSD_IDECLK_comp.txt (2.46 kB - downloaded 260 times.)
« Last Edit: October 20, 2009, 12:09:40 PM by FlynDice »
Logged
e280v2    fuzev1 2gb   clip+4gb   8GB Transcend cl6 uSD    access to fuzev2 4GB       clip+2gb R.I.P.

Offline funman

  • Developer
  • Member
  • *
  • Posts: 645
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1207 on: October 21, 2009, 08:07:16 AM »
The slowdown is a bit less than 50% so that looks OK.

We should compare to the OF transfer speed in USB mode
Logged
a wise man said: "a wise man said"

Offline Urutoraman

  • Member
  • *
  • Posts: 5
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1208 on: October 21, 2009, 09:24:36 PM »
Is this the right forum to post?
I was using Rockbox fine on my e280v2 for a week and decided to load the current build 2 days ago. Now I am getting this *PANIC* SD Transfer Error: 0x8 all the time. r23313. 

Have an A-Data MicroSDHC with 4GB.

Weird part is that if I navigate through the Database menu I can get songs to play from the microSD card but after a few minutes it skip and I get the SD Transfer error again.

Tried a chkdsk but it didn't found any issues on the SD card.

Any thoughts?

By the way... Good work.
Logged

Offline FlynDice

  • Developer
  • Member
  • *
  • Posts: 166
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1209 on: October 22, 2009, 12:17:18 AM »
Have I done this correctly?  I tried to add ISR INT_MCI1 and INT_IDE to demonstrate that MCI_MASK1(INTERNAL_AS3525) is masking for INT_IDE.  I made  MCI_MASK0(drive)=0 and MCI_MASK1(drive) = MCI_ERROR | MCI_DATA_END(ie I swapped them).  My aim was to run the code using the two Mask1 registers(replacing the current MASK0 registers) to show that the internal drive MASK1 is doing masking on INT_IDE.  Rockbox operates quite normally this way but is my logic sound enough to draw this conclusion?

Yes I know we don't need them right now but I'd like to understand how these things are put together better..... ;)

see http://pastie.org/664619

EDIT:

@ Urutoraman

I would be interested in knowing what system/debug/View disk info reports for the Speed of your card.
The internal is displayed first then if you push the select button it should cycle through your disks.
« Last Edit: October 22, 2009, 12:22:10 AM by FlynDice »
Logged
e280v2    fuzev1 2gb   clip+4gb   8GB Transcend cl6 uSD    access to fuzev2 4GB       clip+2gb R.I.P.

Offline funman

  • Developer
  • Member
  • *
  • Posts: 645
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1210 on: October 22, 2009, 06:45:59 AM »
flyndice: my way to be sure my code runs is to add a panicf() in the isr ;)
Logged
a wise man said: "a wise man said"

Offline Urutoraman

  • Member
  • *
  • Posts: 5
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1211 on: October 22, 2009, 09:21:59 PM »
Quote from: FlynDice on October 22, 2009, 12:17:18 AM
EDIT:

@ Urutoraman

I would be interested in knowing what system/debug/View disk info reports for the Speed of your card.
The internal is displayed first then if you push the select button it should cycle through your disks.
Here it is

D% Rev 1.9
Prod: 0/2008
Ser#: 0x193025CB
M=1D, 0=AD
Blocks: 0x00775400
Speed: 50Mbits/s
Taac: 10.0ms
Nsac: 0 clk
R2W: *2
IRMax: 10.45mA
IWMax: 100.200mA

 
Update:
r23327-091024 Let me go into Files-><microSD 1> and browse the directories without any error.  But once I choose a song it play for some minutes and then BANG!! *PANIC* SD Transfer Error: 0x08.   Or sometimes it just a black screen and a player reset.
« Last Edit: October 24, 2009, 05:12:59 PM by Urutoraman »
Logged

Offline FlynDice

  • Developer
  • Member
  • *
  • Posts: 166
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1212 on: October 25, 2009, 12:11:15 AM »
@ Urutoraman:

Would you be able to go back and try r23192?  That's just previous to the reimplementation of voltage scaling...


@funman:

Well that was too easy, thanks.  MCI_MASK1 for the internal does indeed mask INT_IDE.  I'm just trying to provide some comic relief with my Rube Goldberg coding tendencies...
Logged
e280v2    fuzev1 2gb   clip+4gb   8GB Transcend cl6 uSD    access to fuzev2 4GB       clip+2gb R.I.P.

Offline funman

  • Developer
  • Member
  • *
  • Posts: 645
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1213 on: October 25, 2009, 07:07:44 AM »
Well that works too :P

About IDE: in system-as3525.c:  system_init() we have this:
Code: [Select]
CCU_SRC = 0x1fffff0 & ~(1<<18); /* FIXME */

bit 18 is the reset bit for an IDE peripheral (there is 2), the internal SD doesn't work if we reset the peripheral, perhaps you have an idea of what we could do to configure it again properly after reset?
Logged
a wise man said: "a wise man said"

Offline Urutoraman

  • Member
  • *
  • Posts: 5
Re: SanDisk Sansa e200 v2, c200 v2, m200 (v2), clip and Fuze
« Reply #1214 on: October 25, 2009, 11:34:20 AM »
Quote from: FlynDice on October 25, 2009, 12:11:15 AM
@ Urutoraman:

Would you be able to go back and try r23192?  That's just previous to the reimplementation of voltage scaling...

If you can point me out where to download it from.  I overwrote mine by mistake.
Logged

  • Print
Pages: 1 ... 79 80 [81] 82 83 ... 129
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.103 seconds with 14 queries.