Re: The EZX machid
Em Sáb, 2009-02-21 às 10:25 +0800, design0 escreveu: > Hi Daniel, > Thanks for your advice.I still can not boot the current kernel. > I tried to on e680 _without_ flashing gen-blob: > [r...@george bootusb]# ./boot_usb setflag usb > Serching for EZX phone: A780/E680 found. > FAILED: setflag: No such file or directory Please update boot_usb. > [r...@george bootusb]# ./boot_usb gen-blob 0 (holding vol+ while > sending the gen-blob) No need to hold vol+ if you previously used "setflag usb" > Serching for EZX phone: A780/E680 found. > Uploading kernel: 100% OK > Uploading params: 100% OK > Calling the kernel... > DONE > (the E680 enter the gen-blob usb mode) > [r...@george bootusb]# ./boot_usb zImage 1741 > Serching for EZX phone: A780/E680 found. > Sending mach id code 1741: 100% OK > Uploading kernel: 100% OK > Uploading params: 100% OK > Calling the kernel... > DONE > (still on the gen-blob usb mode) > The gen-blob which i used is:http://people.openezx.org/wyrm/boot_usb > Is that any wrong my step? Thanks! This should have worked. You can try putting the kernel at /boot/default on the mmc card, and try sending gen-blob via boot_usb, or you can flash gen-blob to the phone. Other than this, I have no clue on whats wrong. -- Daniel Ribeiro
Re:Re: The EZX machid
Hi Daniel, Thanks for your advice.I still can not boot the current kernel. I tried to on e680 _without_ flashing gen-blob: [r...@george bootusb]# ./boot_usb setflag usb Serching for EZX phone: A780/E680 found. FAILED: setflag: No such file or directory [r...@george bootusb]# ./boot_usb gen-blob 0 (holding vol+ while sending the gen-blob) Serching for EZX phone: A780/E680 found. Uploading kernel: 100% OK Uploading params: 100% OK Calling the kernel... DONE (the E680 enter the gen-blob usb mode) [r...@george bootusb]# ./boot_usb zImage 1741 Serching for EZX phone: A780/E680 found. Sending mach id code 1741: 100% OK Uploading kernel: 100% OK Uploading params: 100% OK Calling the kernel... DONE (still on the gen-blob usb mode) The gen-blob which i used is:http://people.openezx.org/wyrm/boot_usb Is that any wrong my step? Thanks! Regards George 在2009-02-20，"Daniel Ribeiro" 写道： >Em Sex, 2009-02-20 às 09:20 +0800, haiqing_liu escreveu: >> Hi all， >> I tried to use the "boot_usb" tool boot the 2.6.29-rc5-ezxdev >> kernel,but failed.the rootfs is placed to the second partition of the SD.I >> cann't see ang information on my E680i while booting the kernel. >> I found some words on >> http://people.openezx.org/wyrm/gen-blob/READMEhttp://people.openezx.org/wyrm/gen-blob/README >> .it says:"Not specifying machid will boot the kernel with machid = 0, this >> is completely bogus, and only the Motorola kernel (or very old ezx kernels) >> will work." >> The machid of the 2.6.29-rc5-ezxdev kernel is 1741(E680i).I think the >> machid which send to the kernel is 0(using the boot_usb tool).if so,Can >> anybody show me how to boot a "new version" ezxdev kernel without install >> the gen-blob on the phone? >> Any advice is welcome.Thanks! >> >> With Regards >> George Liu > >This doesn't look like a machid issue, you are probably getting a kernel >panic on the pxa27x-udc driver because the original blob leaves the UDC >enabled and the mainline driver cant deal with this. You can workaround >this issue using gen-blob or you can try to fix the kernel panic. > >This will boot a current kernel on e680 _without_ flashing gen-blob: > >$ boot_usb setflag usb >$ boot_usb gen-blob 0 >$ boot_usb zImage 1741 > > >This will backup your kernel and flash gen-blob to the device: > >$ boot_usb setflag usb >$ boot_usb gen-blob 0 >$ boot_usb read 0x2 917504 backup-of-motorola-kernel >$ boot_usb flash 0x2 gen-blob > >Setup /boot/menu.lst on the first partition of the card according to the >README on gen-blob dir, and put backup-of-motorola-kernel on the card, >at /boot/default. > >To uninstall gen-blob you enter gen-blob usb mode by holding vol+ while >powering on and do: > >$ boot_usb flash 0x2 backup-of-motorola-kernel > >-- >Daniel Ribeiro > >
Re: E680i status?
Hello. On Fri, 2009-02-20 at 12:06, Shawn Rutledge wrote: > On Fri, Feb 20, 2009 at 11:30 AM, Stefan Schmidt > wrote: > > Sure. Take a look at the old patchset we have in svn. There should be a > > mapping > > driver for E680. > > This one? > http://svn.openezx.org/trunk/src/kernel-2.6/patches/ezx-mtd-map.patch Yes. A short glance let me think that A780 and E680 may be the same. > > Bring it over to the current work in git with the A780 as > > reference and send us the patch. > > > Good question. IIRC correctly the nand was for the /usr stuff. More a guess > > though. Perhpas someone else knows better here. > > Kolja Dummann pointed it out so I updated the wiki with a link to the > other page about flash on Gen1 phones. > > http://wiki.openezx.org/E680i Great, thanks. regards Stefan Schmidt
Re: E680i status?
On Fri, Feb 20, 2009 at 11:30 AM, Stefan Schmidt wrote: > Sure. Take a look at the old patchset we have in svn. There should be a > mapping > driver for E680. This one? http://svn.openezx.org/trunk/src/kernel-2.6/patches/ezx-mtd-map.patch > Bring it over to the current work in git with the A780 as > reference and send us the patch. > Good question. IIRC correctly the nand was for the /usr stuff. More a guess > though. Perhpas someone else knows better here. Kolja Dummann pointed it out so I updated the wiki with a link to the other page about flash on Gen1 phones. http://wiki.openezx.org/E680i
Re: E680i status?
Hello. On Fri, 2009-02-20 at 11:19, Shawn Rutledge wrote: > On Fri, Feb 20, 2009 at 11:03 AM, Stefan Schmidt > wrote: > >> BTW why is it that rootfs has to be loaded from SD? Will it be able > >> to boot from internal flash? Seems like it could if the MTD drivers > >> are part of the kernel (not modules). > > > > The e680i, like other gen1 devices, have a combination of nor and nand > > flash. > > Nor is no problem, we just need the mapping and can read/write/boot from it. > > Antonio added the table for A780 around a week ago, should be easy to do the > > same for E680. > > Anything I can do to help with that? Sure. Take a look at the old patchset we have in svn. There should be a mapping driver for E680. Bring it over to the current work in git with the A780 as reference and send us the patch. > > If you don't care about the original system it should be not to hard to > > replace > > all partionions on NOR with a kernel and rootfs from us. > > How much of each type is there? NOR is enough for a root partition? > Which partitions are which type of flash? > (might be good info I can add to http://wiki.openezx.org/E680i ) Good question. IIRC correctly the nand was for the /usr stuff. More a guess though. Perhpas someone else knows better here. regards Stefan Schmidt
Re: E680i status?
On Fri, Feb 20, 2009 at 11:03 AM, Stefan Schmidt wrote: >> BTW why is it that rootfs has to be loaded from SD? Will it be able >> to boot from internal flash? Seems like it could if the MTD drivers >> are part of the kernel (not modules). > > The e680i, like other gen1 devices, have a combination of nor and nand flash. > Nor is no problem, we just need the mapping and can read/write/boot from it. > Antonio added the table for A780 around a week ago, should be easy to do the > same for E680. Anything I can do to help with that? > The nand chip on the other hand is a problem. It's M-Systems nand > for what drivers are available but due to patents crap we are not allowed to > use > them. So from our view this chip does more or less not exist. Bummer. > If you don't care about the original system it should be not to hard to > replace > all partionions on NOR with a kernel and rootfs from us. How much of each type is there? NOR is enough for a root partition? Which partitions are which type of flash? (might be good info I can add to http://wiki.openezx.org/E680i )
Re: E680i status?
Hello. On Fri, 2009-02-20 at 10:38, Shawn Rutledge wrote: > On Fri, Feb 20, 2009 at 8:16 AM, Daniel Ribeiro wrote: > >> I'm glad to have X with the touchscreen, and usbnet working at least. > >> I would really like to get bluetooth and power management working > >> next. It will if I build a kernel with OpenEmbedded, right? > > No. > > No to what? Oh I know now to use the openezx git rather than OE for > kernels, I guess that's what you meant. Newest OE build the kernel from git as well. The point is more about that it is easier to build the kernel outside when you do a lot hacking on it. > BTW why is it that rootfs has to be loaded from SD? Will it be able > to boot from internal flash? Seems like it could if the MTD drivers > are part of the kernel (not modules). The e680i, like other gen1 devices, have a combination of nor and nand flash. Nor is no problem, we just need the mapping and can read/write/boot from it. Antonio added the table for A780 around a week ago, should be easy to do the same for E680. The nand chip on the other hand is a problem. It's M-Systems nand for what drivers are available but due to patents crap we are not allowed to use them. So from our view this chip does more or less not exist. If you don't care about the original system it should be not to hard to replace all partionions on NOR with a kernel and rootfs from us. regards Stefan Schmidt
Re: E680i status?
On Fri, Feb 20, 2009 at 8:16 AM, Daniel Ribeiro wrote: >> What about the one here: >> >> http://people.openezx.org/wyrm/images/latest/ >> >> Is it supposed to be "universal" for all the phones? > > Yes, and its 2.6.29-rc5. > Power status and bluetooth depends on the baseband processor on E680, so > you will need gen-blob flashed to the phone to get it working. I realized that last night, but so far haven't succeeded, because when I boot that 2.6.29 kernel (with modules) the mtd devices are not working. On IRC somebody mentioned that I could use boot_usb to flash genblob? Hmm like this I guess: https://lists.gnumonks.org/pipermail/openezx-devel/2008-December/002473.html Is that what I should do, or it's better to figure out what's wrong with the MTDs first? >> I'm glad to have X with the touchscreen, and usbnet working at least. >> I would really like to get bluetooth and power management working >> next. It will if I build a kernel with OpenEmbedded, right? > No. No to what? Oh I know now to use the openezx git rather than OE for kernels, I guess that's what you meant. When I built my own kernel that way, it did not find rootfs. (MMC/SD drivers not working?) BTW why is it that rootfs has to be loaded from SD? Will it be able to boot from internal flash? Seems like it could if the MTD drivers are part of the kernel (not modules).
Re: E680i status?
Em Ter, 2009-02-17 às 00:24 -0700, Shawn Rutledge escreveu: > I managed to boot with images from here > > http://www.angstrom-distribution.org/unstable/images/a780/ > > but there are some things not working (no power status, I think it's > not charging the battery, no bluetooth). Are there any E680i-specific > builds being posted anywhere? Is 2.6.23 the newest kernel that works? > What about the one here: > > http://people.openezx.org/wyrm/images/latest/ > > Is it supposed to be "universal" for all the phones? Yes, and its 2.6.29-rc5. Power status and bluetooth depends on the baseband processor on E680, so you will need gen-blob flashed to the phone to get it working. > I'm glad to have X with the touchscreen, and usbnet working at least. > I would really like to get bluetooth and power management working > next. It will if I build a kernel with OpenEmbedded, right? No. -- Daniel Ribeiro
