Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - nhorlock

Pages: [1] 2
1
Open Embedded / Bitbake Fails With Gnu Gcc
« on: May 09, 2005, 05:50:29 am »
Quote
I've moved on to the next problem now (still in gcc) it is failing to build libiberty due to an undefined function __builtin_expect which is supposedly a gcc builtin for branch prediction hinting.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78811\"][{POST_SNAPBACK}][/a][/div]

Thanks to help from #oe (PB__ in particular for his suggestion) I've found that this one was because I was using a shell that had previously been used to build an old Sharp/Opie and thus was finding an old gcc  from the embeddix toolchain.

So a tip for you all. Start with a clean shell and check your gcc before you start. I wasted a lot of time trying to figure out what was wrong.

Neil

2
Open Embedded / Bitbake Fails With Gnu Gcc
« on: May 08, 2005, 04:39:14 pm »
Savannah didn't seem to be broken, insofar that webcvs was fine. I tried gcc.gnu.org as well and that also failed. In the end I tried to pull it manually (despite not having the slightest clue where to move it to after I'd got it. That worked. I then tried bitbake again and it also started to pull down gcc.

The question is was this pure coincidence that savannah came back just when I tried the manual pull or (more likely) is the fact that I exported CVS_RSH=ssh and set my CVSROOT manually prior to the last attempt anything to do with this? I thought bitbake controlled all the environmental settings but this would suggest I am wrong.

I've moved on to the next problem now (still in gcc) it is failing to build libiberty due to an undefined function __builtin_expect which is supposedly a gcc builtin for branch prediction hinting.

Ho hum, I'll get there in the end.

Neil

3
Open Embedded / Bitbake Fails With Gnu Gcc
« on: May 07, 2005, 05:08:17 pm »
I'm trying to build something (anything right now would be a start!) on OE but bitbake is unable to retrieve some or all of the gcc pavkage becuase the anonymous CVS @ savannah.gnu.org just timesout. How can I get around this?

Neil

4
6000 - Tosa / Restore A Sl-6000 Sharp Rom Without Using Nand
« on: March 28, 2005, 04:27:25 pm »
Quote
So my files are fine? good. I dind't know q+t could have such problems.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=72495\"][{POST_SNAPBACK}][/a][/div]
Your files are problem free. Though the cut down updater.sh does ignore zimage.bin files but given that I was (I believe) misusing it, this may well be expected behaviour.

I knew that whatever the problem was it was likely to be me. Too many others had been fine, but dsespite following the two main "sharp restore" threads I was getting nowhere fast. I had spent ages trying different things and ,you know how it is, I suspect that I'd made a silly error early on and then gone down the wrong path completely with the updater script (Am I correct in thinking that the updater.sh is not intended/expected to work with original Sharp ROMs?), then by the time I got back to trying your zip archive again I'd probably stopped checksumming the files and thus shot myself in the foot.

Thanks for a great site (externe.net) it answered a lot of questions. The NAND map is very nice.

Neil

5
6000 - Tosa / Who has a 6000?
« on: March 27, 2005, 06:33:33 pm »
Got my 6000L On Thursday. Bought it from a guy in the US via ebay. Only downside was getting stung for VAT on the import which always annoys me as if Iwere buying in the UK I would not have to pay VAT on second hand goods.

Nice bit of kit. Can't wait for the next OZ to appear. Have finally got the Sharp ROM back on it and can flash 'tween the two at will. Sharp ROM is quite well put together, the wireless setup wizard is easy to use for example, however it lacks the broad software base of OZ so it won't stay once the keyboard issues and the power/suspend issues are history.

Neil

6
6000 - Tosa / Restore A Sl-6000 Sharp Rom Without Using Nand
« on: March 27, 2005, 06:18:36 pm »
Quote
I need some help here as  I'm obviously missing something.

Well, I've done it. Sharp rom is now back. In the end it appears to be a hardware issue. My observations on the updater.sh and soforth still appear to be correct however the key point for me seems to be that updater.sh is simply not needed to restore the Sharp ROM (perhaps implying that this thread is now the wrong place for this post!).

The final clue was the Wiki page here which states something like "if lights keep flashing, fiels are corrupt". Well I'd already checked them a number of times but finally I thought to try a different CF card and it worked first time (reset+q+t).

Problem solved. Thanks to whoever put the Wiki entry up as it served to force me to try the new card. I'm still puzzled as to quite what is wrong with the other card it shows no errors, but that is for another day.

Neil

7
6000 - Tosa / Setting Up Wireless Network On Openzauru
« on: March 27, 2005, 03:10:56 pm »
In case anyone looks here for help.

The latest README attached to the 6000 OZ3.5.2 download (www.openzaurus.org of course) gives good instructions for setting up wireless. This worked fine for me using WEP as well. In fact it behaves better than my SL5500 with D-Link CF card. Note: Heed the advice to avoid the GUI setup though as that seems to throw a spanner in the works. The only slight issue I've had, and it may well be down to my Belkin wireless bridge, is an occasional slow response when requesting a new lease. At the moment I have to bring up the interface manually but that is just my laziness, after a reboot, fire up a console and type 'ifup wlan0', the udhcpc call gives up, goes into background after 3 attempts, and never seems to recover. If this occurs simply type 'ifdown wlan0' and repeat the ifup, it normally takes less than 3 attempts to get the lease.

Neil

8
6000 - Tosa / Restore A Sl-6000 Sharp Rom Without Using Nand
« on: March 26, 2005, 09:37:24 pm »
Guys,
I recently acquired a 6000L which is flashed to OZ3.5.2 which is fine (its issues aside) but I want to flash back to Sharp just to know that I can and to compare the two products (while I'm waiting for 3.5.3). However I need some help here as  I'm obviously missing something. Please bear with me as I want to cover all the steps I've taken so that anyone else following in my footsteps can relate their experience with mine (and hopefully achieve a resolution)

step 1) I've got my CF card and unzipped the 1.12 ROM zip from externe (and also tried one from thegrantclan.org which is identical). Using these files alone and attempting a flash using reset+q+t leads to infinitely flashing LEDs (presumably something is not found).
step 2) Switching to reset+Pwr+OK then selecting update from CF gives more info (as expected...)  /mnt/cf/updater.sh is not found.
step 3) is to install updater.sh, again I've used the externe/zaurus/flash updater.sh and this is found and runs OK.

Note: The updater.sh flashes just the RO filesystem and then the "Maser" (presumably a typo for master). It does not find zImage and this is obvious when you take a look at the updater.sh as the zip file has zimage.bin but updater looks for various capitalizations of zImage but never for a .bin extension.

step 4) rename zimage.bin to zImage and try again from step 2.
Kernel is found (hooray) and successful RoFS is installed OK. Mas(t)er also apparent a success.
Problem solved you'd think....'fraid not.

The reboot proceeds to stream "/usr/sharp/etc/launch.conf can not open file" messages until init intervenes due to too many respawns.

Could it be that the initfs.bin also needs to be installed. It is not mentioned by the updater.sh but does feature in the updater.pro file. However as this is a pure guess and given that many in this thread profess to having been succesful with this process I can only assume that I have done something wrong. Any ideas?

My problem sounds like that experienced by jeffbarish in the "How to Restore a 6000L ...." thread, indeed he clearly had the zimage.bin issue but he appears to have got round that using "reset+d+p" but for me I get "CF Update Can not initialize."

Finally, I am just trying the updater.sh from thegrantclan which is more comprehensive, though amusingly it seems to expect zImage.bin and not find zimage so remember to rename it back again (if you've previously renamed it). Still no luck though, exactly the same problem, it does however try to mount a filesystem as part of the process but apparently fails so perhaps this is where the problem lies........

Help!

Oh well its 2:30 AM here so I'd better get some sleep, my daughter will be expecting to go hunt for some easter eggs in a few hours.

9
Angstrom & OpenZaurus / Bitbake Help Please
« on: January 14, 2005, 04:14:39 pm »
Si,
Thanks for the pointer to COW. The patches have got me a lot further . I think however that my PC is just too feeble. Time to get a new linux dev box I think, the old desktop hand me downs just don't cut it any more.

cheers

Neil

10
Angstrom & OpenZaurus / Bitbake Help Please
« on: January 13, 2005, 06:21:33 pm »
Hi guys,
Following my last post (konq-e build) I now have everything setup for a build. Once I realised that bit keeper is still required and that I could indeed trust the Wiki, all became much easier. The only real pain was mandrake 10 that I am using did not have the Makefile installed as part of the python rpm and thus psyco would not cooperate. In the end I uninstalled all the python rpms and built from source, psyco had no problem after that.

The whole setup appears a lot slicker than my old build setup based on the original sharp env I setup.

Now to the question. I have a nice clean build env setup and as far as I can tell to build konqueror I simply type "bitbake konqueror" from my build dir and away it should go. However, in practice what happens is bitbake comes back with
Note: Using cache in BLAH/BLAH
Note: Handling BitBake files: (0001/2000) [0%]. It then proceeds to work its way through the 2000 files. It will get so far and then slow down and even (apparently) stop for  long periods and if left to run it will eventually exit with "Killed". It seems to abort in this way pseudo randomly. I am just running it again with debug on to see if it offers up any more info but it has been running for over an hour now and is currently hung on

Code: [Select]
NOTE: Handling BitBake files: - (1453/2000) [72 %]DEBUG: bbmake: parsing /home/neil/src/open-embedded/openembedded/packages/opie-today-weatherplugin/opie-today-weatherplugin_cvs.bb
for ages (at least 15 mins maybe  more) any ideas anyone? Surely this is not normal is it? What have I missed?

Neil

11
Angstrom & OpenZaurus / How To Build Konq-e For Oz
« on: January 10, 2005, 05:25:20 pm »
Cheers Mickey,

I'll wander through the wiki page again. Last time I looked it seemed to reference BitKeeper in places and BitBake in others and assumed it was therefore incorrect. however looking at it once again I think that I had misunderstood the talk of subversion replacing bitkeeper as the release note clearly says that this is the case for core but makes no reference to anything else. Am I right in thinking that I need both subversion and bitkeeper now? I'll spend time sorting it out for myself and I'll put back any additional comments into the Wiki if I think they might help others.

As for libjpeg. I suspected that it might already be built that way but had no way to easily check. That still leaves me with a Konq/e that can (repeatably) hang my Z or gives black squares. I am using my Z as a remote for a media server running SlimServer. The Slimserver software has an interface skin designed for handhelds and is pretty cool with the one exception that browsing my collection by album cover art is prone to result in a reboot of the Z. The internal jpeg lib was my only good lead :-( back to the drawing board. Second best guess is memory leak. Browsing artwork is going to send a large number of images .....

Anyhow, time to get my build environment up to scratch first.

Neil

12
Angstrom & OpenZaurus / How To Build Konq-e For Oz
« on: January 09, 2005, 07:29:00 pm »
The konqueror-embedded that is part of the opie feed is broken for jpegs and can crash your Z in some cases but in most cases just results in black squares. The fix (apparently) is to not depend on internal jpeg support of qt but to require the external jpeg libs. I want to build a new konq ipk for OZ with external jpeg support and hopefully with the kflashpart add-in (who knows if this'll work!). However I am just confused as to where to start establishing a decent build environment now.

Does anyone have a basic, start from scratch guide to getting in a position to build for the current opie/OZ environment the webpages seem confused with the amount of changes that have taken place recently so I've no idea where to get things from.

13
Cheers both for the replies. Lardman is right there is no other process locking the device.

The PC is running Mandrake 9, the interface (being my handiwork) is most likely to be at fault. However in its defence it works in most situations
Dive -] PC
Dive -] Palm
Palm -] PC
Palm -] Zaurus

The only thing that doesn\'t work is Dive Computer -] Zaurus.
The interface is not much more than an a signal amplifier to boost the signal of the dive computer. It boosts enough to be used by both the palm and the PC but if the Z is very particular then perhaps this is the problem. Is there anyway to determine the voltage levels at the interface without an external scope of some form?

I feel a trip to Maplins  might be in order, I\'ll grab a breakout box to be able to force a couple of signal high to match those seen when using Palm -] Z.

14
I am trying to use my Z to download data from my dive computer. The program works fine on my laptop and can receive data from the computer itself or from my palm IIIx (running dive computer emulation software). However on the Z it will only receive data sent by the Palm and not when it is sent direct from the Dive computer.

My guess is that it is one of two things:-
1) The voltage threshold on the Z is too high for my dive computer interface to drive.
2) The Z is more fussy about serial line signals than the PC.

Does anyone have any thoughts on this?
Anyone suceeded in connecting a Zaurus to an UWATEC Aladin dive computer?

Detailed Note:
Setup is a Z thin serial cable into either the palm serial cradle or a home made interface.
On PC the interface/palm plug directly in to the serial port.

Using a peice of serial scope software on the laptop and the Z I can see that DCD and CTS are raised when the palm sends but none are raised by the interface whether on the Laptop (works) or the Z (Doesn\'t work).

Any suggestions would be appreciated.

Neil

15
5x00 General discussions / OpenZaurus, a horror story..
« on: April 13, 2004, 06:46:50 pm »
I\'ve had various interesting games with SD but almost all of them are down to using ext2 and not being careful about where things are installed. If you stuff anything onto an SD it is safest to ensure that it is not going to be open when you suspend as my experiments showed that this would always lead to gradual decay into corruption.  Thus it is fine for data storage, and stuff that is not open for more than the time it takes to read it but forget any thought of relocating shared libs or apps there. (Side note to developers. It is not uncommon to mmap files rather than read and write, if you port or write an app that does this please bear in mind what may happen upon suspend...)

Having sadi that the description above seems much more basic than this and though I have not experienced it with SD I have had real problems with moving Smart Media between devices and this eventually came down to propietary extensions used by certain manufacturers. In my case (using the excellent pretec CF/SM card to mount the SM) if it was formatted on my dell laptop the Z would be fine. If However I had previously formatted it on my Olympus camera, the Dell would see it fine and write to it with no problems at all but the Z would not see the files at all.  This left me in a real panic one time when I was reflashing my Z!!! Is there a chance that the SD card has been formatted on a device such as a camera rather than a PC.? The cure for me was simply to reformat to VFAT on the laptop, the camera still loves it, the Z still works and all is well once again.

Pages: [1] 2