Support and General Use > Hardware

H320 running CF card - problems

<< < (2/3) > >>

petur:

--- Quote from: kokoon on June 12, 2008, 08:17:39 AM ---hi. i'm running RockBox, a very recent version (like a week old), with the custom H300 bootloader that cam be found on http://www.rockbox.org/twiki/bin/view/Main/CFModGuide

the adapter is the kind everybody has, the with a jumper i had to bend.

the card is Transcend 32gb 133x

generally it works. i can transfer music to and from the device, i can play. while playing, there aren't any problems. but sometimes on startup, i get the following errors:

1. totally randomly, but usually when player was off overnight/more than a few hours.
on boot, right after the "Batt: ..." line (that's line 3), it clears the screen and reports:
I03:AddrErr
at 003F2FD2

2. when attaching the USB cable to the turned-off device, again after the "Batt" line 3, "Bootloader USB mode" flashes for a fraction of a second and then clears the screen and reports:
I03:AddrErr
at 003F2B4E

in both cases, i have to reset the player, either by pressing "play", waiting it boots OF, waiting some more so it reports HDD error, then shut it down. or i can just use a safety pin to reset the player.

it's quite annoying actually, are there any other reports of this kind of problem?

--- End quote ---
You are, in fact, probably hit by a bug in the current svn bootloader. I have this issue on my h340 with 80GB disk. The plan is to have a debug session during devcon next week.

So this is not CF related at all....

kokoon:
so... any news? has this been fixed?

and where can i find the bootloaders?

FLN:
I just did the CF Mod today, and have similar problems like kokoon...

I use the modified Bootloader from http://www.rockbox.org/twiki/bin/view/Main/CFModGuide, a 16GB 133x CF card from Transcend and the following CF to IDE adapter: http://www.dealextreme.com/details.dx/sku.10886.

When I try to start Rockbox, I always get the following error code:
I03: AddrErr
at 003F35DA

But my H320 is booting properly when I connect the turned off player to USB and then disconnect it.
I have tried several builds with always the same result.

Does anyone have a hint what I could try to resolve that problem?

Thank you!

kokoon:
hey FLN.
i spoke to petur last week and he told me it's a known bug in the bootloader and that it's still not fixed. supposed to be some timing issue. he also told me who's the guy working on that but i forgot.

so... your version of the problem seems a bit more awkward than mine, too bad. i mean, i can live with mine, i just have to reboot it sometimes. you going to investigate?

FLN:
hi kokoon,

thanks for your reply. I just found out that it could take up to 6 or 7 resets to start my player. At first I didn't try that often. It seems that it needs more resets after charging or connecting it via USB.

Navigation

[0] Message Index

[#] Next page

[*] Previous page