From BUG Wiki

Contents 1 Normal BUG Behavior 1.1 Observable boot sequence behavior: 1.2 The sequence of the BUG booting: 2 Typical BUG problems 2.1 Network 2.2 BUGbase: 2.3 BUGlocate: 2.4 BUGcam2MP: 2.5 BUGview 2.6 BUGmotion 2.7 Handylink Connector 2.8 Applications:

Normal BUG Behavior

Observable boot sequence behavior:

1. Engage the power switch
2. Front (blue) LEDs will flash (go on and off) momentarily
3. BUGbase LCD backlight will illuminate, and the Bug logo will display:
4. If Camera module(s) and LCD module(s) are attached, they will power up at kernel/redboot load time, so the Camera module's flash will be on, and the LCD's backlight will be on. There will be no display on the LCD module. The camera module's flash will illuminate later than the LCD module's backlight. This is normal.
5. After approximately 10 seconds the backlight on the BUGbase LCD will shut off momentarily, then the animation on the front LCD will change to a dynamic image to indicate boot activity.
6. The camera module's flash should then shut off, the LCD backlight may remain on.
7. The base LCD animation will stop after approximately 30 seconds, when the java libraries are loading. At this point Xserver and Xeyes will appear on the LCD module (if attached), the clock will display on the BUGbase LCD along with the attached modules' icons. The display on the BUGbase LCD, if all modules are attached, should resemble this:
8. The LCD module should display this:

The sequence of the BUG booting:

1. Power on->Redboot->Load Kernel->mount rootfs on Memory Card->load OS->load OSGi.
2. Steps 1 and 2 regard power. If there is a failure here, it is likely a fail in power.

1. Steps 3 and 4 regard Redboot and the Kernel loading. If BUG hangs, it is likely that the Root file system on your Memory Card is corrupted.

Typical BUG problems

Network

Problem: I can telnet/ping/ssh into my BUG, but I can't see it in Eclipse.

Solution: This may mean that your BUG libraries aren't loaded properly. Please shutdown your BUG and restart it. If the problem is persistent, you can telnet/ssh into BUG and cat /var/log/concierge.log. If there are many exceptions, this most likely indicates that the Memory card is corrupted. Please follow these instructions to upgrade your BUG Memory card.

Problem: I can't connect to my BUG.

Solution: Verify that the boot procedure is proceeding as normal, and make sure you follow the instructions on the start page to the letter.

Problem: I don't know the password for telnet/ssh on my BUG.

Solution: It is defaulted to root/root.

Problem: What is my BUG's IP?

Solution: If the instructions on the start page were followed exactly, the BUG's IP will be 10.10.10.10, and is accessible from the Host machine.

Problem: I can telnet into my BUG, but my BUG cannot access the internet.

Solution: Presently, connection bridging is only supported on Linux systems. The instructions on the start page show you how to forward incoming traffic on the host system to your BUG. To verify that your BUG can access the internet, telnet/ssh into the command line, and ping 4.2.2.2. If the host is unreachable, please double check that the instructions were followed correctly. Please note: Ubuntu/debian based Linux systems are the target for our instructions. If you are using other distributions you may have slightly varied instructions, and are welcome to post in the discussion forums about their success.

BUGbase:

Problem: My bug won't boot.

Solution: Try to find out at what state the boot failure is occurring.

1. 1. If BUG freezes with blue-lights on steady (steps 1-2 in normal boot behavior above), this is a power problem and you should contact our support team.
   2. If BUG freezes after the blue lights flash and the Bug logo is displayed, this usually indicates that the Memory card is corrupted and needs to be flashed. Please follow these instructions to upgrade your BUG Memory card.
   3. If BUG freezes at any other point, it means that the Memory card may have been corrupted in the /opt/concierge folder. You can telnet/ssh into BUG and cat /var/log/concierge.log. If there are many exceptions, this most likely indicates that the Memory card is corrupted. Please follow these instructions to upgrade your BUG Memory card.

Problem: My BUG won't charge.

Solution: More than likely this is a problem with the AC adapter. Please fully discharge your BUG (leaving it on with all modules attached), attach the power supply, and look for a red LED at the rear of your BUG near the power plug. If there is no red LED, try to gently jostle the AC adapter. If the LED intermittently illuminates, this is an indication that you have a bad AC adapter. If no amount of jostling results in a red LED, this may be an indication that the BUGbase has a power problem. Either way you should contact our support team.

BUGlocate:

Problem: I can't get a GPS fix.

Solution: This is due to the large amount of EM noise generated by the BUGbase. We are in the process of choosing an appropriate external antenna to ship to all users who have bought the Hiro P edition of the BUGbundle.

BUGcam2MP:

Problem: My camera flash flickers sometimes and it seems like it crashes my BUG.

Solution: If the Camera module is positioned opposite the LCD module (camera in slot 1, LCD slot 3).

Problem: My camera light is stuck on.

Solution: This is an indication that it's not booting fully. Please try to navigate the menu using the joystick, if it is unresponsive, it is likely your BUG is not booted all the way. See the above section.

BUGview

Problem: Why can't I use the LCD in slots 0,2? Or I want to use two LCD's and I can't. Or I just see static when I plug in my LCD or I heard that I should plug my LCD into specific slots, which ones were they? Why?

Solution: The LCD module is under heavy development, it's performance should be greatly enhanced soon. As of right now, the LCD module should only be inserted in slots 1,3, the slots directly above and below the joystick because that is what we currently support in software. This is where we have x-server rendering, and this is where LCD-screen touch events are polled from. The camera module should not be positioned opposite the LCD module (I.e. if LCD in slot 1, camera should be in either slots 0 or 2). We're looking to remedy this as well.

Problem: My LCD module is doing the flash-light. I don't see xserver running, and I don't see xeyes. I don't see static either, and it's plugged into slots 1,3.

Solution: This is a problem we've been trying to track down. Preliminarily, it looks like a problem with the BUGbase and you should contact our support team.

BUGmotion

Problem: I need high-resolution accelerometer data. The API doesn't support it.

Solution: The old BUG API (R1.1, SDK 1.0.0.5) had an elementary Accelerometer API. It is now much more robust. Please refer to BUGlevel application for an example of how to access the hardware at very high resolutions.

Handylink Connector

Problem: Network access with handylink?

Solution: We are trying to get some of these cables made for our more dev-oriented customers. We have posted some DIY instructions here.

Applications:

Problem: My application won't start.

Solution: Ensure that they you have networking set up, that you sent the application to 10.10.10.10 in the Dragonfly (the BUG SDK), and that the required modules for the application are attached to your BUG. A great resource for any application or programming questions is to check out our discussion forums.