• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 [2] 3
16  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: August 29, 2009, 12:43:11 AM
Well, you're right in general.
But in this particular case, if I remember well, the patch affects the uImage binary (i.e. the kernel itself), not the modules.
I'm not 100% sure anyway...
17  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: August 28, 2009, 10:46:14 AM
The patch must be applied on the source code, not on the binary. You have the recompile the kernel.
Anyway, cross-compiling the kernel is not very difficult. See http://www.computingplugs.com/index.php/Building_a_custom_kernel
I used the mainline source code, the config and patches of http://sheeva.with-linux.com/sheeva/, added this patch, and cross-compiled.
18  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: August 27, 2009, 11:58:27 AM
1. no, as far as I know, this patch is not included in any official kernel. The main reason is that it's not necessary for every SD card. Applying this patch disables highspeed, even if the SD card would work correctly with it

2. I don't know. I don't have a Polaroid SDCard.

If you need, I have a 2.6.30.4 kernel with this patch, based on the config of http://sheeva.with-linux.com/sheeva/
19  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD support in u-boot on: August 21, 2009, 12:21:10 AM
westyd1982, I had exactly the same error when formatting my 8Gb SDHC card in ext3.
Once I formatted it in ext2, the error disappeared.
20  Hardware and U-Boot firmware / U-Boot stuff / Re: MMC/SD support in u-boot on: August 09, 2009, 06:27:40 AM
Hi all, I'm using the uboot version bundled with the Sheevaplug installer alpha 6.
It can boot on a ext2 SD card, but not on a ext3 SD card (it gives a "bad magic number" in this case)

Is ext3 supported by u-boot? Will it be in the future, or did I miss a step to make it work?

This is how I format my SD card in ext2 :
mkfs -t ext2 -I 128 /dev/mmcblk0p1

If I format it in ext3 :
mkfs -t ext3 -I 128 /dev/mmcblk0p1
U-boot won't boot on the SD card (bad magic number)
21  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: July 28, 2009, 01:13:09 PM
The plug is up for more than 2 days... That's great!
Thank a lot philipl for this patch

PS : my SDHC card is a Crucial CT8GBSDHC
22  Linux Stuff / Kernel / Re: Reliable SD support by disabling highspeed operations on: July 26, 2009, 02:16:36 PM
I also applied this patch on a 2.6.30.3 mainline kernel and used the plug for a few hours.
It looks like it took rid of the -110 errors : without this patch, it took a few minutes before these errors to show up.

I run a few speed tests on the SDHC, based on http://www.computingplugs.com/index.php/SheevaPlug_Performance
As expected, the read speed is reduced : 9.1 Mb/s.
The write speed doesn't seem to be affected :  7.5 Mb/s

That's great news : my plug is finally stable, and it boots on the SD card.

Anyway, it's a pitty we have to reduce the speed. I hope a better solution will be found
23  Linux Stuff / Kernel / Re: SD card support on: May 24, 2009, 01:28:39 PM
My own observations are very similar :

1) Same fact : before I opened the plug, I never managed to have any SD card work. I have tested 3 different cards : a brand new Crucial SDHC 8Gb, an old Canon SD 32Mb, and an old Panasonic SD 256Mb.

2) I tested several different kernels, including orion and mainline, but none of them worked before I opened the plug. Currently, I use a mainline kernel, with patches coming from orion (especially the mvsdio one)

3) Same thing : from a cold boot (with the plug opened), all my cards work reliably when I boot on NAND. I currently don't manage to boot directly from SD (I mean, use a rootfs from SD, even if the kernel is on NAND), but it's probably another problem

4) From a soft reboot, that depends : sometimes it works, sometimes it does not. I did not notice any difference between SD and SDHC card, but I did not have enough time to make complete tests

5) What I can say, it's that a cold reboot (unplug / replug) is always safe. A soft reboot sometimes leads to -110 errors, or undetected cards
24  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 24, 2009, 08:25:30 AM
OK I tried again with the "feroceon.cpu arp_examine" line, and with 2000kHz, as requested.
It works too, even if the same kind of warnings appear (see log below)

Code:
sudo ./runme.sh  **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1049). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1110). Workaround: increase "set remotetimeout" in GDB
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 32.932339s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1002). Workaround: increase "set remotetimeout" in GDB
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 117.655731s
 **** U-boot should be up and running now. Open your console ...
25  Linux Stuff / Kernel / Re: SD card support on: May 24, 2009, 02:59:06 AM
I am also puzzled.

As Philipl said, it seems that the SD cards stop working after a soft reboot (even with the sheevaplug opened).
I tried that with a 2.6.30-rc6 patched kernel, and a recent uBoot with SD support, through the installer alpha-5 (http://plugcomputer.org/plugforum/index.php?topic=323.0)

If I unplug and replug it, the SD card works... Quite strange.
26  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 24, 2009, 02:51:05 AM
Thanks a lot for your answers.

Changing the frequency was the right thing to do : it worked with 500kHz (but it didn't work with 1000kHz). Maybe it's worth changing this for next version.
See the log below : there seems to be some warnings anyway

Code:
sudo ./runme.sh  **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
500 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1241). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1020). Workaround: increase "set remotetimeout" in GDB
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 52.464920s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1024). Workaround: increase "set remotetimeout" in GDB
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1178). Workaround: increase "set remotetimeout" in GDB
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 188.052399s
 **** U-boot should be up and running now. Open your console ...


After that, the sheevaplug reboots, flashes, reboots... and it works.

First thing that surprises me : it seems that it boots much faster than before. Is this due to UBIFS?
The rootfs is also directly useable : no patch needed for apt or dns lookups, and only 3 update with apt-get upgrade.

I love this installer, because it really eases all the process of flashing, and modifying the uboot parameters. And you get a working and up-to-date OS, with an up-to-date kernel.
Thank you for the good job!
27  Linux Stuff / Kernel / Re: SD card support on: May 23, 2009, 01:35:12 PM
Wow, thanks philipl for the tip.
I was fighting with SD cards and sheevaplug for weeks.
I tried with 3 different SD cards (SD ans SDHC), and kernels (mainline, orion, different patches etc). I had -110 errors every time.

As you proposed, I opened the sheevaplug, and plugged it again : boom, all SD cards are detected by the kernel and can be mounted readwrite (I'm currently using mainline 2.6.30-rc6 with mvsdio patch).
That's great news, because I still thought I had a software problem.
On the other hand, the behavior is quite strange : If I close the plug again (with the 4 screws), the -110 errors are back. It looks like it only works if the sheevaplug is opened.
Could it be due to the red push-button inside the plug? Maybe it's pushed when the plug is closed...
Or maybe it's due to the heat of the power supply next to it?

I'm currently trying to use the SD card (actually a 8Gb SDHC) as my root filesystem (keeping the kernel in NAND). With the plug opened or closed, I get the -110 errors. Maybe it's because I did not patch uBoot, or because the howto has been removed from the FAQ (found http://www.openplug.org/plugwiki/index.php?title=Frequently_Asked_Questions&oldid=413#Make_an_SD_card_be_the_root_filesystem in the history, but it has been removed in the latest version of the page : http://www.openplug.org/plugwiki/index.php?title=Frequently_Asked_Questions)

Philipl, do your SD cards work if you close the sheevaplug? Did you manage to use an SD card as your root file system?
28  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 23, 2009, 10:49:03 AM
Hi,

first of all, I think this is a great idea to make an installer.

Anyway, I didn't manage to make it work on my computer & sheevaplug.
Maybe I did something wrong.

My computer is running Ubuntu 9.04 desktop (x86).
I followed the README.txt in the tar.gz : formatted an USB stick, and put the files in it.
I plugged the mini-USB to the computer, and connected via Putty on /dev/ttyUSB1
Then I ran runme.sh on the computer :

Code:
sudo ./runme.sh
 **** Preparing environment variables file ...
 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Error: JTAG communication failure, check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x3F. tap=feroceon.cpu pos=0 expected 0x1 got 3
Warn : Could not validate JTAG chain, continuing anyway...
Warn : value captured during scan didn't pass the requested check:
Warn : captured: 0x0F check_value: 0x01 check_mask: 0x0F
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
Error: Target not examined yet
Runtime error, file "../scripts-linux/openocd/config/board/sheevaplug.cfg", line 21:
   
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplug

The sheevaplug reboots at this moment, but nothing has been flashed.

The README explains that we should in this case disconnect/reconnect the sheevaplug, or even unplug/plug back it.
I did it several times, and even restarted the computer : the same error happens.

It seems that line 20 of sheevaplug.cfg is executed (which restarts the sheevaplug), but line 21 fails ("halt 0")

I tried with or without putty connected, with or without an OS launched on the sheevaplug : always the same error.

Any ideas?
29  Linux Stuff / Linux distributions / Re: Kernel panic - not syncing: No init found on: April 25, 2009, 01:40:33 PM
The problem was apparently coming from the commands after the flash.
If I use the commands from Rev1.0, I can boot correctly :

Code:
setenv bootargs 'console=ttyS0,115200 mtdparts=nand_flash:0x400000@0x100000(uImage)ro,0x1fC00000@0x500000(rootfs)rw root=/dev/mtdblock2'
setenv bootcmd 'nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
saveenv
reset

This worked with the jffs2 posted at http://djpandemonium.com/plug/SheevaPlug_FileSystem.zip

With the latest file downloaded from the website (v1.2), the mount gave me this error :
Code:
JFFS2 notice: (294) check_node_data: wrong data CRC in data node at 0x00069000: read 0xc5585480, calculated 0xa78a6243.
JFFS2 warning: (294) jffs2_do_read_inode_internal: Truncating ino #22 to 30236 bytes failed because it only had 16384 bytes to start with!

For now, I'll keep the jffs2 of pandemonium (thank you), and try to upgrade ubuntu to final version.
30  Linux Stuff / Linux distributions / Re: Kernel panic - not syncing: No init found on: April 25, 2009, 11:45:44 AM
I managed to make ubuntu boot correctly!
I simply applied the instructions of the previous version of documentation : Rev1.0, instead of Rev1.2

I'll try to find out which exact command was wrong...
Pages: 1 [2] 3