Menu
▾
▴
simpad-general — This list is to discuss general problems of linux with SIMpad
You can subscribe to this list here.
| 2003 |
Jan
(27) |
Feb
(16) |
Mar
(107) |
Apr
(67) |
May
(227) |
Jun
(174) |
Jul
(128) |
Aug
(68) |
Sep
(64) |
Oct
(25) |
Nov
(78) |
Dec
(18) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(24) |
Feb
(26) |
Mar
(20) |
Apr
(26) |
May
(22) |
Jun
(11) |
Jul
(31) |
Aug
(11) |
Sep
(69) |
Oct
(5) |
Nov
(11) |
Dec
(16) |
| 2005 |
Jan
(10) |
Feb
(6) |
Mar
(2) |
Apr
(19) |
May
(4) |
Jun
(18) |
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(15) |
Nov
(7) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Piotr G. <bi...@ma...> - 2005-04-21 20:01:09
|
Dnia 20-04-2005, =B6ro o godzinie 12:24 +0200, Michael 'Mickey' Lauer napisa=B3(a): > Now that we agreed on the merger on Familiar Linux, OpenZaurus and > OpenSIMpad, > we need to find a new name for this unified distribution. > Since this has to be discussed globally, we setup a Wiki page @ > http://handhelds.org/moin/moin.cgi/NewDistroNames > There you can suggest names (including pros and cons) as well as enhanc= e > the page to discuss alternatives. Great. BTW.: Could someone update us with fresh information about OpenSimpad? What is te status of OpenSimpad 0.9 and if it's know date of lunch stable version? Is there any beta images avaliable? Waiting for any information. Regards Piotr |
|
From: Schweizer W. <wal...@si...> - 2005-04-21 16:02:09
|
Yes, go ahead. Is Bitkeeper still required? Regards Walter > -----Original Message----- > From: sim...@li... > [mailto:sim...@li...]On Behalf Of Tim > Wentford > Sent: Wednesday, April 20, 2005 12:19 PM > To: ope...@li...; > sim...@li... > Subject: Re: [Simpad-general] Merging Familiar Linux, OpenZaurus and > OpenSimpad >=20 >=20 >=20 > > After the move to the new linux-eabi OpenZaurus, OpenSimpad=20 > and Familiar > > will be binary compatible with each other and debian-arm.=20 > All 3 distros > > are already being built from the same source, namely OpenEmbedded. > > > > The release managers of those projects would like the three=20 > projects to > > merge and create a small, fast, stable and professional=20 > Linux distribution > > for all kinds of devices (handhelds, webpads, settop-boxes,=20 > POS systems). > > > > Back in the days when we unified as part of the=20 > OpenEmbedded team, we > > found it > > would be better to keep the known "brand names" for while=20 > we are in the > > transition > > from the non-OE releases to the OE-based releases. After a couple > > of successful OE-based releases, we now think it's the time=20 > to do the > > next step and complete the merger. > > > > What are your opinions on this subject? >=20 > My opinion, FWIW, is yes, go ahead. >=20 > Cheers > Tim=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: New Crystal Reports XI. > Version 11 adds new functionality designed to reduce time involved in > creating, integrating, and deploying reporting solutions.=20 > Free runtime info, > new features, or free trial, at:=20 http://www.businessobjects.com/devxi/728 _______________________________________________ Simpad-general mailing list Sim...@li... https://lists.sourceforge.net/lists/listinfo/simpad-general |
|
From: Schweizer W. <wal...@si...> - 2005-04-21 16:00:05
|
Hi Guilhem I cannot give you the BSP for SIMpad because it is proprietary. Sorry Walter > -----Original Message----- > From: sim...@li... > [mailto:sim...@li...]On Behalf=20 > Of Guylhem > Aznar > Sent: Saturday, April 16, 2005 10:57 PM > To: sim...@li... > Subject: [Simpad-general] various stuff >=20 >=20 > Hello >=20 > A quick update on various things >=20 > 0. wince support >=20 > Could anyone please send me the files to create a wince image on the > platform builder? >=20 > I think I would need simpad-bsp.msi, drivers and any information on > the memory parameters. >=20 > I'd like to play with dual boot. >=20 > 1. kernel 2.4.29 >=20 > I have manually applied the various patches since 2.4.25 to reach > 2.4.29. An =FCberpatch is on > externe.net/zaurus/simpad-bluetooth/2.4.29-simpad.patch.gz >=20 > It still misses some of Till latests patches, and has 2 bugs:=20 > the green > light is always on, and hidp (bluetooth keyboard) crashes the kernel. >=20 > Besides that it should be ok. Feel free to include it and distribute > it. >=20 > 2. sandisk : using wifi and storage at the same time >=20 > I have a good hypothesis on why the wifi and storage part of the > sandisk connect plus 128 Mb+wifi can't be used on the simpad at the > same time: as indicated on dstridi.de forum, some io ports must be > disabled in config.opts. Some ppl with that fix succeeded. However > doing the same didn't work on the simpad because... 2.4 internal > pcmcia support is used, instead of pcmcia-cs modules! (that's written > in config.opts). I'm compiling a new kernel to use pcmcia-cs modules > but it has stability problems. >=20 > Anyway it should be possible to use wifi and pcmcia at the same > time ! >=20 > 3. internal bluetooth - remaining components >=20 > While working on a BT module for Chris Martin, I damaged one of the > fpc ports on my addon board (short circuited 2 pins that are too close > to unsolder them, and cut 2 lines on the integrated circuit). If > anyone is interested and has some time, I can offer the board + fpc > connector + fpc cable to connect to the unused DECT connector on a SL4 > to any serial stuff (ex: bt module). It should be possible to save it, > if you have a good (thin) thermostated soldering iron, and in the > worst case the necessary equipment to print and burt an new integrated > circuit board to solder the fpc connector. >=20 > Pics available if needed to estimate the "unsoldering" work to be > done. >=20 > --=20 > Bien =E0 vous - Best regards, > Guylhem P. Aznar >=20 > --=20 > *@externe.net =20 > http://externe.net > P=E9rim=E9/Deprecated: @oeil.qc.ca, @metalab.unc.edu,=20 > @ibiblio.org, @7un.org > GPG: 92EB37C1 DD11C9C9 20519D01 E8FA1B11 42975AF7=20 http://externe.net/pubkey ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick _______________________________________________ Simpad-general mailing list Sim...@li... https://lists.sourceforge.net/lists/listinfo/simpad-general |
|
From: Michael 'M. L. <mi...@tm...> - 2005-04-20 10:24:23
|
Now that we agreed on the merger on Familiar Linux, OpenZaurus and OpenSIMpad, we need to find a new name for this unified distribution. Since this has to be discussed globally, we setup a Wiki page @ http://handhelds.org/moin/moin.cgi/NewDistroNames There you can suggest names (including pros and cons) as well as enhance the page to discuss alternatives. -- Regards, Mickey. ------------------------------------------------------------------ Dipl.-Inf. Michael 'Mickey' Lauer <mi...@tm...> ------------------------------------------------------------------ |
|
From: Tim W. <tim...@ho...> - 2005-04-20 10:20:23
|
> After the move to the new linux-eabi OpenZaurus, OpenSimpad and Familiar > will be binary compatible with each other and debian-arm. All 3 distros > are already being built from the same source, namely OpenEmbedded. > > The release managers of those projects would like the three projects to > merge and create a small, fast, stable and professional Linux distribution > for all kinds of devices (handhelds, webpads, settop-boxes, POS systems). > > Back in the days when we unified as part of the OpenEmbedded team, we > found it > would be better to keep the known "brand names" for while we are in the > transition > from the non-OE releases to the OE-based releases. After a couple > of successful OE-based releases, we now think it's the time to do the > next step and complete the merger. > > What are your opinions on this subject? My opinion, FWIW, is yes, go ahead. Cheers Tim |
|
From: Michael 'M. L. <mi...@tm...> - 2005-04-19 15:54:12
|
Greetings, big things are going on in the OpenEmbedded world. After the move to the new linux-eabi OpenZaurus, OpenSimpad and Familiar will be binary compatible with each other and debian-arm. All 3 distros are already being built from the same source, namely OpenEmbedded. The release managers of those projects would like the three projects to merge and create a small, fast, stable and professional Linux distribution for all kinds of devices (handhelds, webpads, settop-boxes, POS systems). Back in the days when we unified as part of the OpenEmbedded team, we found it would be better to keep the known "brand names" for while we are in the transition from the non-OE releases to the OE-based releases. After a couple of successful OE-based releases, we now think it's the time to do the next step and complete the merger. What are your opinions on this subject? -- Regards, Mickey. ------------------------------------------------------------------ Dipl.-Inf. Michael 'Mickey' Lauer <mi...@tm...> ------------------------------------------------------------------ |
|
From: Guylhem A. <si...@ex...> - 2005-04-16 20:56:35
|
Hello A quick update on various things 0. wince support Could anyone please send me the files to create a wince image on the platform builder? I think I would need simpad-bsp.msi, drivers and any information on the memory parameters. I'd like to play with dual boot. 1. kernel 2.4.29 I have manually applied the various patches since 2.4.25 to reach 2.4.29. An =FCberpatch is on externe.net/zaurus/simpad-bluetooth/2.4.29-simpad.patch.gz It still misses some of Till latests patches, and has 2 bugs: the green light is always on, and hidp (bluetooth keyboard) crashes the kernel. Besides that it should be ok. Feel free to include it and distribute it. 2. sandisk : using wifi and storage at the same time I have a good hypothesis on why the wifi and storage part of the sandisk connect plus 128 Mb+wifi can't be used on the simpad at the same time: as indicated on dstridi.de forum, some io ports must be disabled in config.opts. Some ppl with that fix succeeded. However doing the same didn't work on the simpad because... 2.4 internal pcmcia support is used, instead of pcmcia-cs modules! (that's written in config.opts). I'm compiling a new kernel to use pcmcia-cs modules but it has stability problems. Anyway it should be possible to use wifi and pcmcia at the same time ! 3. internal bluetooth - remaining components While working on a BT module for Chris Martin, I damaged one of the fpc ports on my addon board (short circuited 2 pins that are too close to unsolder them, and cut 2 lines on the integrated circuit). If anyone is interested and has some time, I can offer the board + fpc connector + fpc cable to connect to the unused DECT connector on a SL4 to any serial stuff (ex: bt module). It should be possible to save it, if you have a good (thin) thermostated soldering iron, and in the worst case the necessary equipment to print and burt an new integrated circuit board to solder the fpc connector. Pics available if needed to estimate the "unsoldering" work to be done. --=20 Bien =E0 vous - Best regards, Guylhem P. Aznar --=20 *@externe.net http://externe.n= et P=E9rim=E9/Deprecated: @oeil.qc.ca, @metalab.unc.edu, @ibiblio.org, @7= un.org GPG: 92EB37C1 DD11C9C9 20519D01 E8FA1B11 42975AF7 http://externe.net/pubk= ey |
|
From: Devon H. O'D. <do...@of...> - 2005-03-24 14:32:15
|
Hey, I'm trying to port SIMpad support over to Plan 9 (which already has some support for the SA1110 in its code for the iPaq), and have a couple of questions. First I should say that I'm not terribly familiar with the hardware, nor Linux' source layout, so I'm pretty in the dark at the moment regarding how this all works. I'm not unfamiliar with kernel concepts or programming though, so a decent explination should clear stuff up :) My questions at the moment (there will probably be more later, but I'll save those for then ;)): o Where does the SIMpad bootloader expect my kernel to be? I should theoretically be able to already boot a minimal Plan 9 kernel if I know where the loader has put me (as well as some other things like whether MMU is enabled or not). =20 o It appears possible to boot from the network. What devices are supported for this configuration (it would save me a good bit of work and time than having to write a new image onto the flash every time I fix something)? o To prepare me for the future, is anybody familiar with where I can find (preferably for no cost) information on the hardware inside the SIMpad SL4 (i.e. datasheets)? I've looked but have had no luck finding anything. Any help for these three points would be quite appreciated. Thanks, Devon |
|
From: Reiner K. <pd...@t-...> - 2005-03-05 18:36:36
|
Greetings, I managed to flash (simpad slc) the new bootloader and 0.9-rc1. The appearance is nice and it feels fast and responsive. Two quick questions: Is there a feed for this release somewhere ? df says that 644 blocks are used in /home in a newly flashed image, yet the directory is completely empty ?? Thanks for pointers, Reiner |
|
From: Frederic D. <fre...@m4...> - 2005-02-18 16:17:49
|
I found this message by Till Harbaum containing the full patch for this. It would be a great think to include it in the OE build. http://www.handhelds.org/hypermail/oe/18/1842.html Fred |
|
From: Frederic D. <fre...@m4...> - 2005-02-18 15:13:06
|
(sorry for those who got this on opensimpad.org, I realized that simpad-general was maybe more appropriate) Hello, I noticed that, when the simpad opens a connection on the serial port, the DTR (data terminal ready) pin is always low. Some peripherals use this to detect that a terminal is on the line, and I would like to use it to power my Palm Portable Keyboard (yes, very soon we might have a very cheap and comfortable keyboard for the simpad!). unfortunately, arch/arm/mach-sa1100/simpad.c in the openembedded kernel doesn't seem to support it, although I found another version of this file <http://externe.net/zaurus/simpad-bluetooth/simpad.c> which _seems_ to support it (but I didn't try it, and it seems to be modified for a 128M simpad). Is there a chance that DTR/RTS supports comes into the mainstream OE kernel one of these days? Fred |
|
From: Michael 'M. L. <mi...@tm...> - 2005-02-11 18:09:54
|
Warning: CrossPosted - please watch your replies! Hi guys, I just got confirmation from Rick Lehrbaum @ ziffdavis that upon my request OpenEmbedded has been added to the list of embedded linux distributions for the 2005 Embedded Linux Market Survey: http://www.linuxdevices.com/cgi-bin/survey/survey.cgi?id=01282005155246 So, please go ahead and fill out the survey and vote on OpenEmbedded, if you are using an OpenEmbedded based distribution, e.g. Familiar Linux, OpenZaurus, OpenSIMpad, etc. That way we make people aware that we exist and perhaps draw more eyes upon our work. -- Best Regards, Mickey. ------------------------------------------------------------------ Dipl.-Inf. Michael 'Mickey' Lauer <mi...@tm...> ------------------------------------------------------------------ |
|
From: geron <g.e...@gm...> - 2005-02-02 10:57:14
|
The short strory: I forgot to erase the flash before serloading blupdater. The long story: Everything went fine during flashing and running blupdater. Countdown was running, pad was identified correctly, old loader was backed up, new loader was flashed, no error messages. So, I confidently pressed reset. But instead of rebooting, the pad immediately powered off. Pressing the power button made the backlight flicker shortly. Holding it down kept the backlight on while holding. If holding a longer time, the screen became white slowly. Time for JTAG. I always wanted to get familiar whith it, now I had the right motivation. ;-) I soldered the jumpers, made a cable and compiled the software. Thanks to Walter for his excellent JTAG-HowTo! To find out what happened, I read out the flash form 0x00000 to 0x80000 using JTAG. 0x00000 to 0x3FFFF was completely 0x00 at 0x40000 was the bootldr-params.jffs2 starting whith 0x85 0x19 0x01 0xE0 the rest was 0xFF Obviously, the padding bytes and the bootldr-params got flashed, but why didn't the bootldr? I decided to recreate the starting situation and having a look into blupdater. I JTAG'ed my old backup of /dev/mtd/0 which I did a year ago. This way, I got back the PBL and bootloader 2.5.3 in one single step w/o altering other parts of the flash. Guess, I never was that happy to see the tartan pattern on the screen. ;-) Then I serloaded blupdater again and during the countdown I pressed reset. After reboot, the flash procedure was skipped and I got the serial console. Chris, this works very well, nice idea! While booting, the kernel threw some warnigs: Inode #310 was a directory with children - removing those too... Inode #311 was a directory with children - removing those too... Cannot remove child "Tag", ino #0, because it doesn't exist Cannot remove child "Root", ino #0, because it doesn't exist Cannot remove child "Repository", ino #0, because it doesn't exist Cannot remove child "Entries", ino #0, because it doesn't exist Inode #390 was a directory with children - removing those too... Now I got the suspicion... And yes, this is what my root directory looked like: / # ls -l drwxr-xr-x 1 1000 100 0 Jan 1 00:00 bin drwxr-xr-x 1 1000 100 0 Jan 1 00:00 boot -rw-r--r-- 1 1000 100 97438 Jan 1 00:00 bootldr-SIMpadCL-2.21.13.bin.gz drwxr-xr-x 1 0 0 0 Jan 29 2005 bootldr-SIMpadCL-2.21.13.bin.md5 drwxr-xr-x 1 0 0 0 Jan 1 00:00 bootldr-SIMpadSL-2.21.13.bin.gz drwxr-xr-x 1 0 0 0 Dec 2 2003 bootldr-SIMpadSL-2.21.13.bin.md5 -rw-r--r-- 1 1000 100 318 Jan 1 00:00 bootldr-params.jffs2.gz drwxr-xr-x 1 0 0 0 Feb 26 2004 bootldr-params.jffs2.md5 drwxr-xr-x 1 0 0 0 Jan 1 00:00 dev drwxr-xr-x 1 0 0 0 Jan 29 2005 etc drwxr-xr-x 1 1000 100 0 Dec 17 2003 lib -rwx------ 1 1000 100 5023 Jan 1 00:00 linuxrc drwxr-xr-x 1 0 0 0 Sep 4 2004 mnt dr-xr-xr-x 24 0 0 0 Jan 1 00:00 proc drwxr-xr-x 1 1000 100 0 Jan 1 00:00 sbin drwxr-xr-x 1 1000 100 0 Jan 1 00:00 sys drwxrwxrwt 2 0 0 40 Jan 1 00:00 tmp drwxr-xr-x 1 1000 100 0 Jan 1 00:00 usr drwxr-xr-x 1 1000 100 0 Jan 1 00:00 var Note that bootldr-SIMpadSL-2.21.13.bin.gz and bootldr-SIMpadSL-2.21.13.bin.md5 are flagged as directory with a size of 0! This situation Chris's linuxrc wasn't able to handle, of course. Without digging deeply into linuxrc, I guess since both files were affected, the MD5 check didn't trigger. And since there was actually no bootldr file or the size was 0, only padding bytes got flashed. Really bad luck. Anyway, I erased the flash did all again, and now I've got a running 0.9.0. Very impressive, especially the speed improvement! Really good work, guys! Now, what do we get out of it? Chris, the 1st step in your blupdater HowTo should be "Erase The Flash". But what with the 16MB devices? Do we need a padded blupdater image? geron |
|
From: Michael 'M. L. <mi...@tm...> - 2005-02-02 09:42:57
|
Ok, thanks Peter and Geron, I'll change it to 11000 in the OE kernel. -- Regards, Mickey. ------------------------------------------------------------------ Dipl.-Inf. Michael 'Mickey' Lauer <mi...@tm...> ------------------------------------------------------------------ |
|
From: geron <g.e...@gm...> - 2005-02-02 07:33:30
|
Peter Pregler wrote: > Thus my suggestion for an experiment to find > that values: just go up with the external voltage and see at what > point the LED goes on for charging. The charging LED is triggered at 10.2V with nearly no hysteresis. So, I would suggest a value of 11000 for MIN_SUPPLY. geron |
|
From: Peter P. <Pet...@em...> - 2005-01-31 20:02:57
|
On Mon, 2005-01-31 at 19:42 +0100, Michael 'Mickey' Lauer wrote: > > Looking through the kernel patches at OE, I came across the line > > 2004/03/31 mickey | +#define MIN_SUPPLY 12000 /* Less th= en > > 12V means no powersupply */ > >=20 > > Maybe someone of the kernel coders can verify this and change the value= to > > 11000 or 10000 for more reliability. >=20 > Sounds reasonable (to me at least). Juergen, Walter, Ralf, can I get a > confirmation from you? The original code is by J=C3=BCrgen, but the usage is by me. So I feel qualified too. :) The original definition is more or less this: /* * We have two types of batteries a small and a large one * To get the right value we to distinguish between those two * 450 Units =3D=3D 15 V */ #ifdef SMALL_BATTERY=20 #define CALIBRATE_SUPPLY(a) (((a) * 1500) / 51) #define MIN_SUPPLY 8500 /* Less then 8.5V means no powersupply */ #else #define CALIBRATE_SUPPLY(a) (((a) * 1500) / 45) //#define MIN_SUPPLY 14000 /* Less then 14V means no powersupply */ #define MIN_SUPPLY 12000 /* Less then 12V means no powersupply */ #endif The 14V are in the original code on which the code is based. So I guess some smaller value is okay. So I'd say a value smaller than 12V is appropriate. The actual value would be something between 12V and the point the SimPad switches to battery-operation. Note that this is not used for charging which AFAIK is controlled by an extra OS-independent circuit. Thus my suggestion for an experiment to find that values: just go up with the external voltage and see at what point the LED goes on for charging. -Peter =09 |
|
From: Michael 'M. L. <mi...@tm...> - 2005-01-31 18:42:55
|
> Looking through the kernel patches at OE, I came across the line > 2004/03/31 mickey | +#define MIN_SUPPLY 12000 /* Less then > 12V means no powersupply */ > > Maybe someone of the kernel coders can verify this and change the value to > 11000 or 10000 for more reliability. Sounds reasonable (to me at least). Juergen, Walter, Ralf, can I get a confirmation from you? -- Regards, Mickey. ------------------------------------------------------------------ Dipl.-Inf. Michael 'Mickey' Lauer <mi...@tm...> ------------------------------------------------------------------ |
|
From: geron <g.e...@gm...> - 2005-01-31 12:51:36
|
Hi, at the forums, some users reported problems with AC detection. The battery applet shows "Charging, external power disconnected" in that case and the blupdater complains about missing AC power. My pad, while charging, periodically switches between power connected and disconnected, what makes the screen go bright and dark in a 10 seconds intervall. This has nothing to do with the new OE build, the OZ builds have had the same problem. So I hooked up my SL4 to an adjustable PSU and watched the battery applet while slowly turning the voltage control. As soon as the voltage dropped below 12V, the applet showed "external power disconnected". 12V is the nominal voltage of the AC adapter, so putting the threshold at just 12V seems a bit optimistic to me ;-). Looking through the kernel patches at OE, I came across the line 2004/03/31 mickey | +#define MIN_SUPPLY 12000 /* Less then 12V means no powersupply */ Maybe someone of the kernel coders can verify this and change the value to 11000 or 10000 for more reliability. geron |
|
From: Chris M. <chr...@gm...> - 2005-01-24 16:41:06
|
Hello, the bootldr included in the blupdater.img doesn't wotk on 16MB devices. But at least it doesn't brick the pad like the first version for the SL4 did. I need somebody (Peter?) to remove code for the 24MB root partition (and 8MB home) in the latest version for the CL4. Peter already removed the code for the second flash chip as that caused a major problem with the first attempts to upgrade the bootldr with that (when the jffs2 image was installed from this version the writing started at block 0 - which of course overwrote the bootldr). The only thing i can think of that is different from the original attempts from Alex tried while porting is the code defining the 24/8MB partitioning. Peter could you build a version with the corrected code and send it to me. I will modify the blupdater.img and also supply a link for those needing only the bootldr (to salvage that mislung first bootldr installation). Chris Martin -- Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl |
|
From: Rainer K. <rai...@we...> - 2005-01-21 12:12:28
|
I tried the new bootldr on my T-Sinus PAD. Attached is the output after flashing opensimpad-0.9.0rc1_opie.jffs2 with a cf card. If I should do further testing, please contact me. -- Viele Grüsse Rainer Kukasch (rainerk) |
|
From: Krzysztof G. <gra...@mp...> - 2005-01-19 21:14:07
|
I have this answer from Alex: don't use "load bootldr" to reflash the wince one, use "load flash 0" after= =20 you have unprotected the flash. This will solve your issue. I try this and all works very fine Thanks Alex Kris Dnia wtorek, 18 stycznia 2005 21:51, Krzysztof Grandys napisa=B3: > Hi all > I installed opie 0.9.1rc1, first, I serload blupdater.img, second I send > system image with serial port, all works very fine. Now, I`d like come ba= ck > to WinCE and I do: > > boot> set override =3D 1 > setting param <override> to value <1> > boot> pflash 0 40000 0 > addr=3D00000000 > len=3D00009C40 > protect=3D00000000 > Protect=3D00000000 > boot> load bootldr > partition bootldr is a bootldr partition: > requiring a bootldr or parrot image. > After receiving file, will automatically uncompress .gz images > loading flash region bootldr > using ymodem > ready for YMODEM transfer... > 362F95577901AFF5C29BA77867A9D33B simpadSL.rom > 00022EC0 bytes loaded to C0000400 > wrong magic: E3A01E27 > parrot word 0 ->0xE1A00000 > Expected ->0xEA0003FE > parrot word 0x1000 ->0x55AA5A5A > Expected ->0xE321F0D3 > You must load wince BEFORE loading Parrot > Not loading invalid bootldr into flash > > I used simpadSL.rom and simpadCL.rom from sourceforge.net > > And now I dont know what I must do for come back to win_ce, I try serload= - > nothing, I change serial to 38200_8n1 - nothing, I try connect pin1 and 2= - > nothing. > Please help, how can I come back to old bootloader (I dont have CF) > Sorry about my very bad english > Kris > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Simpad-general mailing list > Sim...@li... > https://lists.sourceforge.net/lists/listinfo/simpad-general |
|
From: <kar...@po...> - 2005-01-19 09:23:51
|
i did the switch back to WinCE, but the way i did it...well it was more like brute force than finesy. All i did was to take original bootloader, which you can find here http://sourceforge.net/project/showfiles.php?group_id=65409&package_id=77867 (i have all the bootloaders needed on CD, so mail me and i will send them to you). To tell the truth i couldn't serload some of the bootloaders but in the end i managed it out (please don't ask me how i just don't remember ;-) ) After bootloader loaded i've erased the flash (from bootloader) and next i've copied wince image with serload. I had problems with serloading winCE image with some of the boot loaders, but after trying few bootloaders i've finally serloaded the image. OK i know that it's a way of stupidity, but i'm kinda n00b with linux & embeded devices. Stan >Hi all >I installed opie 0.9.1rc1, first, I serload blupdater.img, second I send >system image with serial port, all works very fine. Now, I`d like come back >to WinCE and I do: > >boot> set override = 1 > setting param <override> to value <1> >boot> pflash 0 40000 0 > addr=00000000 > len=00009C40 > protect=00000000 > Protect=00000000 >boot> load bootldr > partition bootldr is a bootldr partition: > requiring a bootldr or parrot image. > After receiving file, will automatically uncompress .gz images > loading flash region bootldr > using ymodem > ready for YMODEM transfer... > 362F95577901AFF5C29BA77867A9D33B simpadSL.rom > 00022EC0 bytes loaded to C0000400 > wrong magic: E3A01E27 > parrot word 0 ->0xE1A00000 > Expected ->0xEA0003FE > parrot word 0x1000 ->0x55AA5A5A > Expected ->0xE321F0D3 > You must load wince BEFORE loading Parrot > Not loading invalid bootldr into flash > >I used simpadSL.rom and simpadCL.rom from sourceforge.net > >And now I dont know what I must do for come back to win_ce, I try serload - >nothing, I change serial to 38200_8n1 - nothing, I try connect pin1 and 2 - >nothing. >Please help, how can I come back to old bootloader (I dont have CF) >Sorry about my very bad english >Kris > > > >--__--__-- > >_______________________________________________ >Simpad-general mailing list >Sim...@li... >https://lists.sourceforge.net/lists/listinfo/simpad-general > > >End of Simpad-general Digest > > > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 05-01-17 |
|
From: Schweizer W. <wal...@si...> - 2005-01-19 08:47:38
|
Hi Kris Looks like the bootldr requires a special header for downloading the old = bootloader. Bootldr tries to protect itself from accidental overwriting. You need to download the PBL not the normal bootloader first! Regards Walter > -----Original Message----- > From: sim...@li...=20 > [mailto:sim...@li...]On Behalf=20 > Of Krzysztof Grandys > Sent: Tuesday, January 18, 2005 10:51 PM > To: Grupa SIMPAD > Subject: [Simpad-general] How to back to oryginall bootloades >=20 >=20 > Hi all > I installed opie 0.9.1rc1, first, I serload blupdater.img,=20 > second I send=20 > system image with serial port, all works very fine. Now, I`d=20 > like come back=20 > to WinCE and I do: >=20 > boot> set override =3D 1 > setting param <override> to value <1> > boot> pflash 0 40000 0 > addr=3D00000000 > len=3D00009C40 > protect=3D00000000 > Protect=3D00000000 > boot> load bootldr > partition bootldr is a bootldr partition: > requiring a bootldr or parrot image. > After receiving file, will automatically uncompress .gz images > loading flash region bootldr > using ymodem > ready for YMODEM transfer... > 362F95577901AFF5C29BA77867A9D33B simpadSL.rom > 00022EC0 bytes loaded to C0000400 > wrong magic: E3A01E27 > parrot word 0 ->0xE1A00000 > Expected ->0xEA0003FE > parrot word 0x1000 ->0x55AA5A5A > Expected ->0xE321F0D3 > You must load wince BEFORE loading Parrot > Not loading invalid bootldr into flash >=20 > I used simpadSL.rom and simpadCL.rom from sourceforge.net >=20 > And now I dont know what I must do for come back to win_ce, I=20 > try serload -=20 > nothing, I change serial to 38200_8n1 - nothing, I try=20 > connect pin1 and 2 -=20 > nothing. > Please help, how can I come back to old bootloader (I dont have CF) > Sorry about my very bad english > Kris >=20 >=20 > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Simpad-general mailing list > Sim...@li... > https://lists.sourceforge.net/lists/listinfo/simpad-general >=20 |
|
From: Krzysztof G. <gra...@mp...> - 2005-01-18 20:44:06
|
Hi all I installed opie 0.9.1rc1, first, I serload blupdater.img, second I send system image with serial port, all works very fine. Now, I`d like come back to WinCE and I do: boot> set override = 1 setting param <override> to value <1> boot> pflash 0 40000 0 addr=00000000 len=00009C40 protect=00000000 Protect=00000000 boot> load bootldr partition bootldr is a bootldr partition: requiring a bootldr or parrot image. After receiving file, will automatically uncompress .gz images loading flash region bootldr using ymodem ready for YMODEM transfer... 362F95577901AFF5C29BA77867A9D33B simpadSL.rom 00022EC0 bytes loaded to C0000400 wrong magic: E3A01E27 parrot word 0 ->0xE1A00000 Expected ->0xEA0003FE parrot word 0x1000 ->0x55AA5A5A Expected ->0xE321F0D3 You must load wince BEFORE loading Parrot Not loading invalid bootldr into flash I used simpadSL.rom and simpadCL.rom from sourceforge.net And now I dont know what I must do for come back to win_ce, I try serload - nothing, I change serial to 38200_8n1 - nothing, I try connect pin1 and 2 - nothing. Please help, how can I come back to old bootloader (I dont have CF) Sorry about my very bad english Kris |
|
From: Michael G. <mgl...@co...> - 2005-01-10 20:06:03
|
Hi,
I'm trying to build an opie-image with the openembedded toolchain,
using the opensimpad.conf and linux-ulibc as a target.
Now, when bitbake wants to build the kernel, it complains that
arm-linux-ar is missing (and probably other tools too).
Now, the correct name for the binary with ulibc is arm-linux-uclibc-ar
(its was build correctly before).
Where is the correct place to fix the problem, rather than making ~30
symlinks ?
regards,
Michael
|
7 messages has been excluded from this view by a project administrator.