I should note that I didn't come up with these patches, I just got it working with FDT. I forget where I saw it originally, it's been 7 months... It looks like there is a typo in iconnect.h: #define CONFIG_SYS_PROMPT_HISH_PS2 "> " should be #define CONFIG_SYS_PROMPT_HUSH_PS2 "> " I don't know why the parameter list is different in kirkwood_mpp_coby rpress - Debian
bodhi Wrote: ------------------------------------------------------- > @rpress, > > Thanks for the uBoot patch. I'm going to build > with your patch and see if it will make any > difference. If it does not, I'll go ahead and > flash your uBoot image to the iConnect mtd0. It > should run OK with non-DT kernel as before? Yes, I just tested with a non-DT keby rpress - Debian
Yeah I guess I can see it not working with some versions. After all, U-Boot doesn't expect to be run from anything other than a full reset condition. Well if it makes you feel better I just flashed that version again and my device still works: U-Boot 2012.04.01-08086-gfe65963-dirty (Aug 16 2012 - 23:17:18) Iomega iConnect Wireless SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNby rpress - Debian
Ok, I just tested it and it works at address 0x800000 instead. Address 0x600000 does freeze up, I guess it's not valid or something else is there. U-Boot 2012.04.01-08086-gfe65963-dirty (Aug 16 2012 - 22:40:59) Iomega iConnect Wireless SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0 8by rpress - Debian
bodhi Wrote: ------------------------------------------------------- > iconnect => go x600200 > ## Starting application at 0x00000000 ... > > > It stuck here. I recalled the problem about the > uBoot env addr. But looking at your patch, you did > set it to 0xC0000! any idea why it loaded but did > not go? Typo? Shouldn't it be "go 0x600200"by rpress - Debian
I've posted this here before, have you tried it? The patch inside here is for Iomega iConnect and GoFlex Net with device-tree: https://docs.google.com/open?id=0B8FzJlhz-BzBbl9IRWZ6a1J5cTQ And here is the device-tree U-Boot binary for GoFlex Net: https://docs.google.com/open?id=0B8FzJlhz-BzBdXdtdmoxZjhqTk0 But before you flash it, be sure to test it in the old U-Boot by loading iby rpress - Debian
I'm using Motion on an iConnect, which is kirkwood as well. It takes a lot of CPU power as floating point is emulated; I get about 5 FPS at 320x240. What sort of frame rate are you seeing?by rpress - Debian
You've seen my post here? Look in the U-Boot patch file. http://forum.doozan.com/read.php?2,8177,9332#msg-9332 U-Boot needs to be built with 'CONFIG_OF_LIBFDT'. You'll see new options like 'fdt' when doing 'help'. I'm not sure if arcNumber still works once it's built like this. I don't know about zImage either. I know that the U-Boby rpress - uBoot
I am using the mainline 3.6-rc2 kernel, and my DTS file is unchanged. I haven't had any kernel panics on either the iConnect or the GFN. My iConnect is now working again after I fixed U-Boot. It seems pretty stable, so here is the U-Boot (and patch), built 3.6-rc2 kernel (and .config), and DTB file that I am using for those that want to give it a shot. You'll need to set up the U-by rpress - Debian
I also see the "unknown partition table" error, but I figured because I had my RAID set up as two RAID1 arrays under a regular partition table, vs having one RAID1 array and then two partitions under that, it was normal. I have it set this way so I can boot off the first RAID1 array, and it all works awesome, even allowing booting from either drive when the array is degraded. I don&by rpress - Debian
Yes, looks like 'coherent_pool=1M' worked! Thanks. My RAID1 is rebuilding right now, seems to be all a-ok. Is there a way to put this 'coherent_pool' into the DTS file? Somewhere other than the bootargs, as I override this in U-boot because of my RAID...by rpress - Debian
So I think my iConnect RAM problem is caused by U-boot not setting up the registers correctly. I tried to modify them in U-boot but it didn't work, so I need to JTAG now. Anyway when I get that figured out I think it will be ok. Now that just leaves the sata_mv problem on my GFN, it's something pretty simple I'm guessing.by rpress - Debian
Here is my .config file for both: Kernel config And kernel log from the GFN: GFN kernel log I'll get the kernel log from the iConnect later if you want, but in any case it shows "Memory: 128MB = 128MB total"by rpress - Debian
Kurlon Wrote: ------------------------------------------------------- > I haven't tried dropping nr_ports yet, lemmie test > that real quick. > > In the mean time, you're saying you have a GoFlex > Net with 256MB RAM? No, I have two Marvell Kirkwood devices. A GoFlexNet, with 128 MB RAM and now only one working SATA port on 3.6.0-rc1, with nr_ports = <1>by rpress - Debian
Has anyone been able to reproduce my findings, where setting nr_ports = <1> allows booting? My GFN is currently working, but with just one port. And as I mentioned before, the DTS file shows the correct 256 MB of RAM, but the kernel when booting only shows 128 MB. Something else is wrong here.by rpress - Debian
Buttzy10169 Wrote: ------------------------------------------------------- > Im beginning to think that the same way that the > goflex net needed a new uboot to use the 3.2 > kernels and beyond properly perhapt maybe now the > ix2-200 needs a new uboot to be able to use > kernels with device tree? > > edit 1: > rpress How did you compile the new uBoot with the &by rpress - Debian
Hmm another problem I see with my iConnect is that the kernel only shows 128 MB RAM, whereas it is really 256 MB, and the old 3.4 kernel showed 256 MB. The GFN only has 128 MB, so this isn't a problem on that one. The DTS files look correct, I'm not sure where the problem is. How much RAM does the ix2-200 have?by rpress - Debian