Latest posts of: superpat

Show Posts
Pages: 1 2 3 [4] 5 6 ... 10

46	Hardware and U-Boot firmware / Hardware / Re: Is my sheevaplug dead ???	on: February 13, 2010, 07:13:33 AM
Hi, Re the gunge on your power supply components. I am sure that it is leaked electolyte (brown) from more modern caps than I am used to, in the past aluminium foil caps had almost clear electrolyte, we used to call it sal ammoniac years ago. I haven't got a camera handy, so it has to be a description. The only elastomer on mine are very small bright yellow blobs, about pea size, holding down the big capacitor in the centre, and another blob between the alloy heatsink and the small capacitor next to it about 1 inch from the right hand end of the heat sink. I can see the pcb on your power supply is discoloured to the right of the big Cap. Mine is a light fawn colour all over. Googling around.... I am absolutely certain one or more of the caps in your power supply has sicked up its electrolyte. I Googled around and found lots of pictures of BROWN electrolyte. (This appears to be the norm nowadys, not the watery stuff I was more used to seeing when I designed this stuff)! Here is a URL of an article about bad caps and pictures of the exact brown crap thats in your Power supply:- www.pcstats.com/articleview.cfm?articleID=195 I tried to find a spec for the brand of caps in my power supply, yalecon RX, but Googling did not find anything, which worries me a lot. The use of electrolytics in switching power supplies is a very hard application, and "cheapo" caps will not survive for very long. The parameter that screws up the capacitor is the capability of the cap to accept an "ac ripple" component on the dc waveform. This heats the electrolyte, and it expands, and bursts the cap! Read the articles about it. If it is just the caps blown, you may be lucky and changing the caps may fix it, but I don't like the discolored pcb, something else may be blown FINALLY A WARNING..... THIS IS AN UNSHIELDED MAINS POWER SUPPLY. THE VOLTAGES ACROSS THE PRIMARY CAPACITOR ARE NORMALLY SEVERAL HUNDRED VOLTS AND IF YOU GROUND IT THROUGH YOURSELF THE RESULTS MAY BE FATAL TO YOU! EVEN WHEN THE POWER SUPPLY IS UNPLUGGED FROM THE MAINS. TAKE CARE AT ALL TIMES IF YOU ARE WORKING ON A MAINS SWITCHER POWER SUPPLY WITH THE LID OFF! regards Patrick

47	Hardware and U-Boot firmware / Hardware / Re: Is my sheevaplug dead ???	on: February 13, 2010, 04:44:04 AM
Hi, I just opened my PS, it looks like yours minus the brown gunge everywhere. It looks like someone was a bit generous with some brown elastomer to hold the components down! I don't think the caps blew, the electrolyte is nearly clear, and the pressure domes of the caps in your picture haven't bulged In mine there are a few small dabs of cream colored adhesive, holding the big components down. What is your ac mains input voltage to the Sheevaplug? What is the ambient temperature where the plug is sited? Is your mains stable, or do you house lights flicker? (Over ground or underground supply)? Its no good trying to get that Plug working with that supply. Its bu****ed. If you cannot return the sheevaplug, then get a 5V 2A dc wall wart from Ebay and wire that into the red and black wires to the plug pcb. cheers Patrick Edit, Looking at the picture again, I realise I cannot see the pressure relief dome on the smaller cap to the left. If it has bulged and split it would account for the pile of crud from the top of the cap up over the yellow rectangular componet in the top left corner, and the rest could be splash back. Its still a funny colour and consistancy for electolyte though. Also if the cap blew, you should have heard it big time! ( unless the sheevaplug was running unattended! P

48	General Category / General Discussion / Re: eSata SheevaPlug	on: January 24, 2010, 02:43:05 AM
Hi, Just a word of caution regarding Esata drive enclosures. Some of the cheap Chinese enclosures use a 1.5Gb/s bridge chip, and I found them difficult to get the Sheevaplug to recognise when they were connected see this post: http://plugcomputer.org/plugforum/index.php?topic=927.msg6021#msg6021 Although there are probably others, I purchased a Antec MX25 enclosure which works well, "hots plugs" every time. Unfortunately I cannot identify the IC used in the Antec, the top has been abraded to removed manf info, and it has been overstamped "SATALINK" Some performance figures using the Antec enclosure and Samsung drive:- http://plugcomputer.org/plugforum/index.php?topic=927.msg6163#msg6163 regards Patrick

49	Hardware and U-Boot firmware / Hardware / Re: power over ethernet	on: January 22, 2010, 03:10:26 AM
@plugcrazy Not difficult! ( On V1.3 Sheevaplug which I have) Open Sheeva plug case Unplug 5v connector on sheeva SOC PCB. (from mains PSU +5V output) Remove Mains PSU, (just unclip ally box), and mains figure 8 socket Feed POE 5V from POE splitting / conditioning device, through hole where mains figure 8 socket was removed Connect POE 5v to Sheeva pcb, (Would need to obtain suitable +5v connector. standard part, unless you chop the old one off the mains PSU o/p cable and join it to POE 5v) Here are pictures of V1.3 pcb:- http://plugcomputer.org/plugforum/index.php?topic=683.msg4148#msg4148 On last (4th) image Power connector is 4 pin top right, pins are paralleled up for current capability Job done! P

50	Hardware and U-Boot firmware / Hardware / Re: Enabling Esata on V1.3 Sheeva Plug - Progress Report.	on: January 18, 2010, 11:02:03 PM
hi, It is a normal data plug, no power. I boot linux from my sata drive through my modded sheevaplug. I assume that the new esataplugs are similar, i.e. v1.3 pcb's, with all the components fitted. cheers P

51	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 16, 2010, 04:39:47 AM
@johndoe Hi, Welcome ro the madhouse. Firstly. I agree with the previous poster. It is extremely hard to permanently brick the Sheevplug. I would go further and say with a little bit of caution it is difficult to break the hardware either. I have been modding my Sheena for weeks now, running it out of it's case, adding the esata port etc. So long as you are careful and think before you power on, observe the basic static precautions then you will get away with it. Secondly, I agree with you wholeheartedly regarding this forum and wiki and their layout and presentation of information. There are a lot of broken links, a lot of incorrect information, and the information is not very well organized. My particular peeve, is that there is no bug zilla, a place where users can report errors and where the "support" people, (if they existed) could assign severity level and fix time scales. It would save a huge amount of time if users could go to ONE place to look up problems. The people running this forum are MARVELL engineers, but the Plug is a devolved design exercise, by Globalscale, (they have their name on the rev 1 and 1.3 schematics)! There are a lot of very good poeple on this forum, giving a lot of their own time to try to provide answers to all the problems that people are finding. I don't think anyone on the design or manufacture side have ever really given a great deal of thought to the basic support of the product. The implication I get is that "you have bought a dev kit then you buy the warts and all". Realistically how much support can a manufacturer afford to give on a $99 piece of kit? cheers P

52	Hardware and U-Boot firmware / Hardware / Re: Enabling Esata on V1.3 Sheeva Plug - Progress Report.	on: January 15, 2010, 11:16:58 AM
@Takigama Hi, If you go to:- http://www.plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&id=56 You will find an 11 page pdf entitled Sheeva-PowerPlug-V1.3-GTI-090906 Use this to determine the values of the unpopulated components. There are 4 series caps that go in the data feed to / from the esata connector There are 4 caps and a ferrite inductor that produce a pi filter to provide 3.3v to the sata part of the Marvell SOC. The Sheevaplug has an adequate silk screen which will point you where the components have to go. This has been discussed before in this tread, I would suggest you read it carefully! There are even part numbers for the esata connector here. Be warned.. These components are mainly 0402 caps, the size of a grain of salt. They are NOT easy to solder. regards Patrick

53	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 12:15:36 PM
@pingtoo Hi, I just tried out your suggestion to add /bin/sh to the bootargs. What happens now is that the system "stops" and hangs instead of rebooting back to uboot regards P

54	General Category / General Discussion / Re: eSata SheevaPlug	on: January 14, 2010, 11:50:38 AM
@newit This is great news! As you probably know I modified my v1.3 plug, to enable the Esata. It works extremely well, with a good transfer rate! You can read the saga in the hardware section. The price you are asking is reasonable for a commercially enabled version. It is probably less increment than what I had to pay for the extra components and tools to do the fine soldering. However I am very interested in understanding what sata enabled U-boot and kernel images you will be sellling with these sata plugs? I have been using a uboot produced by a poster here "fun" and a kernel I rolled myself. I have set up a bootable sata drive with a deb root file system and a fairly new kernel. all I have to do is power up and in a few seconds I have a deb system running on a 2.5in 500GB drive. (Thats not when I am test Mgillespie's new sheevaplug loader, which blows away my esata uboot ) ! regards Patrick

55	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 10:36:50 AM
@mgillespie crikey! I hope not, but you have got me worried now. What I have done now is too delete ALL references to previous instances of the installer, and I am d/l ing your PM'd location version again! I have reformated the USB stick, and I will start again from scratch. I hope I haven't been stupid here and wasted peoples time. Will keep you posted soonest! P @ pingtoo I need to sort this version doubt out first before I progress with your latest request, I hope you will be patient! P EDIT Panic Over.... I had used the correct latest version which gave the result I posted above. I cleared out all the old stuff so there could be NO possibility of confusion and I got the same kernel exception. The only thing I did wrong was that Gedit had cached an old example of the uboot-nand-custom .txt, instead of displaying the latest one. However the custom config in your latest tar was already set to *nand as you said I have attached the putty log as usual P

56	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 09:55:21 AM
"pingtoo I tried your boot command, ( twice), appeared to "hang" for a minute or so after loading kernel, then suddenly jumped back to uboot with no kernel shell ouput! Putty log attached

57	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 08:50:19 AM
Hi. Well! I just looked at uboot-nand-custom.txt That WAS set to orion_mtd # NAND flash partitions. If using kernel >= 2.6.30 then replace orion_nand with orion_mtd mtdpartitions mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) I changed it to orion_nand and did a complete re-install. This time I got the familiar kernel exception crash. I had a look at the file uboot-dflt.txt, as you suggested, but I cannot see any orion_xxxx terms at all here is the file as it was dl'd:- Quote baudrate 115200 loads_echo 0 ipaddr 10.4.50.165 serverip 10.4.50.5 rootpath /mnt/ARM_FS/ netmask 255.255.255.0 stdin serial stdout serial stderr serial console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) mainlineLinux no CASset min enaMonExt no enaCpuStream no enaWrAllo no pexMode RC disL2Cache no setL2CacheWT yes disL2Prefetch yes enaICPref yes enaDCPref yes sata_dma_mode yes MALLOC_len 1 ethprime egiga0 netbsd_en no vxworks_en no bootargs_root root=/dev/nfs rw bootargs_end :::DB88FXX81:eth0:none image_name uImage bootcmd tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig); bootm 0x2000000; standalone fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; bootdelay 3 disaMvPnp no ethaddr 00:50:43:4e:2a:14 ethmtu 1500 mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs mvNetConfig mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode host yuk_ethaddr 00:00:00:EE:51:81 nandEcc 1bit netretry no rcvrip 169.254.100.100 loadaddr 0x02000000 autoload no enaAutoRecovery yes ethact egiga0 Here is the crash:- Quote UBI: attached mtd1 to ubi0 UBI: MTD device name: "rootfs" UBI: MTD device size: 507 MiB UBI: number of good PEBs: 4056 UBI: number of bad PEBs: 0 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 0 UBI: available PEBs: 4012 UBI: total number of reserved PEBs: 44 UBI: number of PEBs reserved for bad PEB handling: 40 UBI: max/mean erase counter: 22/7 UBI: image sequence number: 0 UBI: background thread "ubi_bgt0d" started, PID 565 UBI device number 0, total 4056 LEBs (523321344 bytes, 499.1 MiB), available 4012 LEBs (517644288 bytes, 493.7 MiB), LEB size 129024 bytes (126.0 KiB) Unable to handle kernel NULL pointer dereference at virtual address 00000018 pgd = df8a4000 [00000018] pgd=1fbea031, pte=00000000, *ppte=00000000 Internal error: Oops: 17 [#1] PREEMPT last sysfs file: /sys/devices/virtual/mtd/mtd1/dev Modules linked in: CPU: 0 Not tainted (2.6.32.3 #1) PC is at __mark_inode_dirty+0xbc/0x160 LR is at __mark_inode_dirty+0x64/0x160 pc : [<c00e2d18>] lr : [<c00e2cc0>] psr: 60000013 sp : df8b5eb8 ip : df8b5eb8 fp : df8b5ed4 r10: 000df017 r9 : df8b4000 r8 : c002dba4 r7 : 0000000a r6 : c05be2a0 r5 : df5258e0 r4 : 00000000 r3 : df52597c r2 : 00000000 r1 : 00000007 r0 : 00000001 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 0005397f Table: 1f8a4000 DAC: 00000015 Process mdev (pid: 566, stack limit = 0xdf8b4270) Stack: (0xdf8b5eb8 to 0xdf8b6000) 5ea0: df5258e0 df46a220 5ec0: 00000000 0000000a df8b5efc df8b5ed8 c012da18 c00e2c70 c00cc730 c06a3280 5ee0: df46a220 df46a220 00000000 df527f00 df8b5f24 df8b5f00 c00cd6e4 c012d9c0 5f00: df8b5f24 df8b5f10 c00db3fc df527f00 df5258e0 00000000 df8b5fa4 df8b5f28 5f20: c00cf73c c00cd68c c0a93500 df125b00 df44e200 01afe402 00000004 df82b000 5f40: 00000000 df8b5f50 00000000 00000000 00000000 ffffff9c 00000000 fffffffe 5f60: df8b5fa4 df8b5f70 c00c19c4 c00c0f4c 00000024 df8b5f80 c00c2ad8 000e3188 5f80: 00000008 df82b000 00000005 00000000 000df008 00000000 00000000 df8b5fa8 5fa0: c002da20 c00cf680 00000000 000df008 000df017 bee0d964 00000003 0000005a 5fc0: 00000000 000df008 00000000 0000000a ffffffff 00000000 000df017 00000000 5fe0: 00000013 bee0d8d0 0007020c 4018dd2c 20000010 000df017 f86d3567 b076c817 [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) from [<c012da18>] (ext2_unlink+0x6c/0x78) [<c012da18>] (ext2_unlink+0x6c/0x78) from [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) from [<c00cf73c>] (do_unlinkat+0xcc/0x154) [<c00cf73c>] (do_unlinkat+0xcc/0x154) from [<c002da20>] (ret_fast_syscall+0x0/0x28) Code: 1a00001c e5953098 e5936038 e5964068 (e5943018) ---[ end trace cadbef7193283b1b ]--- note: mdev[566] exited with preempt_count 1 BUG: scheduling while atomic: mdev/566/0x40000002 Modules linked in: [<c0032d30>] (unwind_backtrace+0x0/0xe0) from [<c042bce0>] (schedule+0x70/0x3fc) [<c042bce0>] (schedule+0x70/0x3fc) from [<c003c430>] (__cond_resched+0x18/0x24) [<c003c430>] (__cond_resched+0x18/0x24) from [<c042c660>] (_cond_resched+0x34/0x44) [<c042c660>] (_cond_resched+0x34/0x44) from [<c00ace20>] (unmap_vmas+0x5f0/0x6d4) [<c00ace20>] (unmap_vmas+0x5f0/0x6d4) from [<c00afb10>] (exit_mmap+0xdc/0x214) [<c00afb10>] (exit_mmap+0xdc/0x214) from [<c0041cc0>] (mmput+0x40/0x110) [<c0041cc0>] (mmput+0x40/0x110) from [<c0045fa8>] (exit_mm+0x148/0x158) [<c0045fa8>] (exit_mm+0x148/0x158) from [<c00475e0>] (do_exit+0x180/0x6c4) [<c00475e0>] (do_exit+0x180/0x6c4) from [<c0031380>] (die+0x17c/0x1a0) [<c0031380>] (die+0x17c/0x1a0) from [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) from [<c042ffac>] (do_page_fault+0x23c/0x258) [<c042ffac>] (do_page_fault+0x23c/0x258) from [<c002d30c>] (do_DataAbort+0x40/0xa0) [<c002d30c>] (do_DataAbort+0x40/0xa0) from [<c042e08c>] (__dabt_svc+0x4c/0x60) Exception stack(0xdf8b5e70 to 0xdf8b5eb8) 5e60: 00000001 00000007 00000000 df52597c 5e80: 00000000 df5258e0 c05be2a0 0000000a c002dba4 df8b4000 000df017 df8b5ed4 5ea0: df8b5eb8 df8b5eb8 c00e2cc0 c00e2d18 60000013 ffffffff [<c042e08c>] (__dabt_svc+0x4c/0x60) from [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) from [<c012da18>] (ext2_unlink+0x6c/0x78) [<c012da18>] (ext2_unlink+0x6c/0x78) from [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) from [<c00cf73c>] (do_unlinkat+0xcc/0x154) [<c00cf73c>] (do_unlinkat+0xcc/0x154) from [<c002da20>] (ret_fast_syscall+0x0/0x28) BUG: scheduling while atomic: mdev/566/0x40000002 Modules linked in: [<c0032d30>] (unwind_backtrace+0x0/0xe0) from [<c042bce0>] (schedule+0x70/0x3fc) [<c042bce0>] (schedule+0x70/0x3fc) from [<c003c430>] (__cond_resched+0x18/0x24) [<c003c430>] (__cond_resched+0x18/0x24) from [<c042c660>] (_cond_resched+0x34/0x44) [<c042c660>] (_cond_resched+0x34/0x44) from [<c00460ec>] (put_files_struct+0x84/0xd4) [<c00460ec>] (put_files_struct+0x84/0xd4) from [<c0047664>] (do_exit+0x204/0x6c4) [<c0047664>] (do_exit+0x204/0x6c4) from [<c0031380>] (die+0x17c/0x1a0) [<c0031380>] (die+0x17c/0x1a0) from [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) from [<c042ffac>] (do_page_fault+0x23c/0x258) [<c042ffac>] (do_page_fault+0x23c/0x258) from [<c002d30c>] (do_DataAbort+0x40/0xa0) [<c002d30c>] (do_DataAbort+0x40/0xa0) from [<c042e08c>] (__dabt_svc+0x4c/0x60) Exception stack(0xdf8b5e70 to 0xdf8b5eb8) 5e60: 00000001 00000007 00000000 df52597c 5e80: 00000000 df5258e0 c05be2a0 0000000a c002dba4 df8b4000 000df017 df8b5ed4 5ea0: df8b5eb8 df8b5eb8 c00e2cc0 c00e2d18 60000013 ffffffff [<c042e08c>] (__dabt_svc+0x4c/0x60) from [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) from [<c012da18>] (ext2_unlink+0x6c/0x78) [<c012da18>] (ext2_unlink+0x6c/0x78) from [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) from [<c00cf73c>] (do_unlinkat+0xcc/0x154) [<c00cf73c>] (do_unlinkat+0xcc/0x154) from [<c002da20>] (ret_fast_syscall+0x0/0x28) BUG: scheduling while atomic: mdev/566/0x40000002 Modules linked in: [<c0032d30>] (unwind_backtrace+0x0/0xe0) from [<c042bce0>] (schedule+0x70/0x3fc) [<c042bce0>] (schedule+0x70/0x3fc) from [<c003c430>] (__cond_resched+0x18/0x24) [<c003c430>] (__cond_resched+0x18/0x24) from [<c042c660>] (_cond_resched+0x34/0x44) [<c042c660>] (_cond_resched+0x34/0x44) from [<c00460ec>] (put_files_struct+0x84/0xd4) [<c00460ec>] (put_files_struct+0x84/0xd4) from [<c0047664>] (do_exit+0x204/0x6c4) [<c0047664>] (do_exit+0x204/0x6c4) from [<c0031380>] (die+0x17c/0x1a0) [<c0031380>] (die+0x17c/0x1a0) from [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) from [<c042ffac>] (do_page_fault+0x23c/0x258) [<c042ffac>] (do_page_fault+0x23c/0x258) from [<c002d30c>] (do_DataAbort+0x40/0xa0) [<c002d30c>] (do_DataAbort+0x40/0xa0) from [<c042e08c>] (__dabt_svc+0x4c/0x60) Exception stack(0xdf8b5e70 to 0xdf8b5eb8) 5e60: 00000001 00000007 00000000 df52597c 5e80: 00000000 df5258e0 c05be2a0 0000000a c002dba4 df8b4000 000df017 df8b5ed4 5ea0: df8b5eb8 df8b5eb8 c00e2cc0 c00e2d18 60000013 ffffffff [<c042e08c>] (__dabt_svc+0x4c/0x60) from [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) from [<c012da18>] (ext2_unlink+0x6c/0x78) [<c012da18>] (ext2_unlink+0x6c/0x78) from [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) from [<c00cf73c>] (do_unlinkat+0xcc/0x154) [<c00cf73c>] (do_unlinkat+0xcc/0x154) from [<c002da20>] (ret_fast_syscall+0x0/0x28) BUG: scheduling while atomic: mdev/566/0x40000002 Modules linked in: [<c0032d30>] (unwind_backtrace+0x0/0xe0) from [<c042bce0>] (schedule+0x70/0x3fc) [<c042bce0>] (schedule+0x70/0x3fc) from [<c003c430>] (__cond_resched+0x18/0x24) [<c003c430>] (__cond_resched+0x18/0x24) from [<c042c660>] (_cond_resched+0x34/0x44) [<c042c660>] (_cond_resched+0x34/0x44) from [<c00460ec>] (put_files_struct+0x84/0xd4) [<c00460ec>] (put_files_struct+0x84/0xd4) from [<c0047664>] (do_exit+0x204/0x6c4) [<c0047664>] (do_exit+0x204/0x6c4) from [<c0031380>] (die+0x17c/0x1a0) [<c0031380>] (die+0x17c/0x1a0) from [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) from [<c042ffac>] (do_page_fault+0x23c/0x258) [<c042ffac>] (do_page_fault+0x23c/0x258) from [<c002d30c>] (do_DataAbort+0x40/0xa0) [<c002d30c>] (do_DataAbort+0x40/0xa0) from [<c042e08c>] (__dabt_svc+0x4c/0x60) Exception stack(0xdf8b5e70 to 0xdf8b5eb8) 5e60: 00000001 00000007 00000000 df52597c 5e80: 00000000 df5258e0 c05be2a0 0000000a c002dba4 df8b4000 000df017 df8b5ed4 5ea0: df8b5eb8 df8b5eb8 c00e2cc0 c00e2d18 60000013 ffffffff [<c042e08c>] (__dabt_svc+0x4c/0x60) from [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) from [<c012da18>] (ext2_unlink+0x6c/0x78) [<c012da18>] (ext2_unlink+0x6c/0x78) from [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) from [<c00cf73c>] (do_unlinkat+0xcc/0x154) [<c00cf73c>] (do_unlinkat+0xcc/0x154) from [<c002da20>] (ret_fast_syscall+0x0/0x28) BUG: scheduling while atomic: mdev/566/0x40000002 Modules linked in: [<c0032d30>] (unwind_backtrace+0x0/0xe0) from [<c042bce0>] (schedule+0x70/0x3fc) [<c042bce0>] (schedule+0x70/0x3fc) from [<c003c430>] (__cond_resched+0x18/0x24) [<c003c430>] (__cond_resched+0x18/0x24) from [<c042c660>] (_cond_resched+0x34/0x44) [<c042c660>] (_cond_resched+0x34/0x44) from [<c00460ec>] (put_files_struct+0x84/0xd4) [<c00460ec>] (put_files_struct+0x84/0xd4) from [<c0047664>] (do_exit+0x204/0x6c4) [<c0047664>] (do_exit+0x204/0x6c4) from [<c0031380>] (die+0x17c/0x1a0) [<c0031380>] (die+0x17c/0x1a0) from [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) [<c0033d88>] (__do_kernel_fault+0x6c/0x7c) from [<c042ffac>] (do_page_fault+0x23c/0x258) [<c042ffac>] (do_page_fault+0x23c/0x258) from [<c002d30c>] (do_DataAbort+0x40/0xa0) [<c002d30c>] (do_DataAbort+0x40/0xa0) from [<c042e08c>] (__dabt_svc+0x4c/0x60) Exception stack(0xdf8b5e70 to 0xdf8b5eb8) 5e60: 00000001 00000007 00000000 df52597c 5e80: 00000000 df5258e0 c05be2a0 0000000a c002dba4 df8b4000 000df017 df8b5ed4 5ea0: df8b5eb8 df8b5eb8 c00e2cc0 c00e2d18 60000013 ffffffff [<c042e08c>] (__dabt_svc+0x4c/0x60) from [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) [<c00e2d18>] (__mark_inode_dirty+0xbc/0x160) from [<c012da18>] (ext2_unlink+0x6c/0x78) [<c012da18>] (ext2_unlink+0x6c/0x78) from [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) [<c00cd6e4>] (vfs_unlink+0x6c/0xdc) from [<c00cf73c>] (do_unlinkat+0xcc/0x154) [<c00cf73c>] (do_unlinkat+0xcc/0x154) from [<c002da20>] (ret_fast_syscall+0x0/0x28) Segmentation fault cheers P

58	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 07:37:34 AM
@mgillespie Just tried your amended (2) version you pm'd me with still same result device full and bad magic number:- terminal output:- Quote debsilch:/home/patrick/sheeva_test_installer/sheevaplug-installer-v1.01# php runme.php nand ** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f) Preparing environment variables file ... reading uboot/uboot-env/uboot-dflt.txt uboot/uboot-env/fw_setenv baudrate 115200 CRC read error on uboot-env.bin: Success uboot/uboot-env/fw_setenv loads_echo 0 uboot/uboot-env/fw_setenv ipaddr 10.4.50.165 uboot/uboot-env/fw_setenv serverip 10.4.50.5 uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/ uboot/uboot-env/fw_setenv netmask 255.255.255.0 uboot/uboot-env/fw_setenv stdin serial uboot/uboot-env/fw_setenv stdout serial uboot/uboot-env/fw_setenv stderr serial uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\) uboot/uboot-env/fw_setenv mainlineLinux no uboot/uboot-env/fw_setenv CASset min uboot/uboot-env/fw_setenv enaMonExt no uboot/uboot-env/fw_setenv enaCpuStream no uboot/uboot-env/fw_setenv enaWrAllo no uboot/uboot-env/fw_setenv pexMode RC uboot/uboot-env/fw_setenv disL2Cache no uboot/uboot-env/fw_setenv setL2CacheWT yes uboot/uboot-env/fw_setenv disL2Prefetch yes uboot/uboot-env/fw_setenv enaICPref yes uboot/uboot-env/fw_setenv enaDCPref yes uboot/uboot-env/fw_setenv sata_dma_mode yes uboot/uboot-env/fw_setenv MALLOC_len 1 uboot/uboot-env/fw_setenv ethprime egiga0 uboot/uboot-env/fw_setenv netbsd_en no uboot/uboot-env/fw_setenv vxworks_en no uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none uboot/uboot-env/fw_setenv image_name uImage uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\; bootm 0x2000000\; uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\; uboot/uboot-env/fw_setenv bootdelay 3 uboot/uboot-env/fw_setenv disaMvPnp no uboot/uboot-env/fw_setenv ethaddr 00:50:43:4e:2a:14 uboot/uboot-env/fw_setenv ethmtu 1500 uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500 uboot/uboot-env/fw_setenv usb0Mode host uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81 uboot/uboot-env/fw_setenv nandEcc 1bit uboot/uboot-env/fw_setenv netretry no uboot/uboot-env/fw_setenv rcvrip 169.254.100.100 uboot/uboot-env/fw_setenv loadaddr 0x02000000 uboot/uboot-env/fw_setenv autoload no uboot/uboot-env/fw_setenv enaAutoRecovery yes uboot/uboot-env/fw_setenv ethact egiga0 reading uboot/uboot-env/uboot-nand-custom.txt uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs rootdelay=5 uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_mtd:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\) uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:c1:e6 uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000 uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200 uboot/uboot-env/fw_setenv bootcmd run recover1 uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000 uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000 uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd Burning uboot and environment variables ... This will take few minutes ... Open On-Chip Debugger 0.2.0 (2009-09-16-09:13) Release $URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS 2000 kHz jtag_nsrst_delay: 200 jtag_ntrst_delay: 200 dcc downloads are enabled Error: couldn't read the requested number of bytes from FT2232 device (19 < 81) Error: couldn't read from FT2232 Error: number of discovered devices in JTAG chain (0) does not match (enabled) configuration (1), total taps: 1 Error: check the config file and ensure proper JTAG communication (connections, speed, ...) Error: trying to validate configured JTAG chain anyway... 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' wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 19.306009s 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' wrote file uboot.bin to NAND flash 0 up to offset 0x00074000 in 66.079620s ** U-boot should be up and running now. Open your console ... debsilch:/home/patrick/sheeva_test_installer/sheevaplug-installer-v1.01# Putty.log is attached cheers Patrick BTW The postman hasn't delivered new box yet, so I can still test for you! P

59	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 05:10:02 AM
Hi No the archive is a gz but its busted:- debsilch:/home/patrick/Desktop# tar -xvzf sheevaplug-installer-v1.01.tar.gz sheevaplug-installer-v1.01/ sheevaplug-installer-v1.01/HOWTO_BUILD.txt sheevaplug-installer-v1.01/uboot/ sheevaplug-installer-v1.01/uboot/uboot-env/ sheevaplug-installer-v1.01/uboot/uboot-env/uboot-mmc-custom.txt sheevaplug-installer-v1.01/uboot/uboot-env/uboot-dflt.txt sheevaplug-installer-v1.01/uboot/uboot-env/fw_setenv sheevaplug-installer-v1.01/uboot/uboot-env/fw_setenv.exe sheevaplug-installer-v1.01/uboot/uboot-env/uboot-nand-custom.txt sheevaplug-installer-v1.01/uboot/uboot.bin sheevaplug-installer-v1.01/uboot/openocd/ sheevaplug-installer-v1.01/uboot/openocd/config/ sheevaplug-installer-v1.01/uboot/openocd/config/interface/ sheevaplug-installer-v1.01/uboot/openocd/config/interface/sheevaplug.cfg sheevaplug-installer-v1.01/uboot/openocd/config/board/ sheevaplug-installer-v1.01/uboot/openocd/config/board/sheevaplug.cfg sheevaplug-installer-v1.01/uboot/openocd/config/target/ sheevaplug-installer-v1.01/uboot/openocd/config/target/feroceon.cfg sheevaplug-installer-v1.01/uboot/openocd/openocd.exe sheevaplug-installer-v1.01/uboot/openocd/openocd sheevaplug-installer-v1.01/win32/ sheevaplug-installer-v1.01/win32/cygwin1.dll sheevaplug-installer-v1.01/win32/cygusb0.dll sheevaplug-installer-v1.01/runme.php sheevaplug-installer-v1.01/installer/ sheevaplug-installer-v1.01/installer/initrd-uImage sheevaplug-installer-v1.01/installer/uImage sheevaplug-installer-v1.01/installer/debian-sheevaplug.sh sheevaplug-installer-v1.01/installer/README.txt sheevaplug-installer-v1.01/installer/modules.tar.gz sheevaplug-installer-v1.01/installer/rootfs.tar.gz gzip: stdin: invalid compressed data--format violated tar: Unexpected EOF in archive cheers Patrick

60	General Category / General Discussion / Re: SheevaPlug Installer with updated kernel, uboot, distro ?	on: January 14, 2010, 04:38:55 AM
Hi. I tried dl'ing your latest version (twice). Each time I could not untar it, reason:- gzip: stdin: invalid compressed data--format violated tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now sorry! cheers Patrick

Pages: 1 2 3 [4] 5 6 ... 10