BeagleBoard-XM: Getting Started (cuz a Raspberry Pi would have been too trendy)

chips & lights & wires, oh my!

i grabbed a new BeagleBoard-XM Rev C from eBay and thought i would document the first steps towards getting a project running with it…

 

WTF is a BeagleBoard-XM?

the BeagleBoard, BeagleBoard-XM, and BeagleBone are a family of small (3.5″), inexpensive, singe-board computers based on the ARM Cortex-A8 CPU. unlike MCU’s such as the Arduino, PIC, NetDuino, these run a full OS (usually Linux or Android). they do however feature some of the same low level interfaces like GPIO, I2C, SPI, etc. there are faster boards (PandaBoard ES, HawkBoard, etc.), but the BeagleBoard has a nice size-to-power ratio and still supports the ubiquitous ARMv7 architecture. the super-cheap Raspberry Pi is all the rage this year, but I went with the BeagleBoard-XM as it had the right combination of ports and features for an upcoming project.

the whole inbred family

 

Let’s Go Shopping

  • Required:
    • BeagleBoard-XM Rev C (or Beagleboard/BeagleBone) (~$150) (Google for somewhere in-stock, Digi-Key usually…, maybe Amazon…)
    • A Quality DC 5V Power Supply, 2 Amp or greater, with Center-positive 5.5 x 2.1mm Barrel Connector ($10) (from Adafruit…) (from Amazon… – this does fit, the tip specs are just listed wrong)
    • USB to RS-232 Serial Cable (~$10) (from Amazon…)
  • Highly Recommended:
  • Optional:
    • HDMI to DVI cable ($-6) (from Amazon…) or an S-Video cable
    • USB Keyboard/Mouse (the Rii Mini Wireless is a handy device that gets the job done, ~$25)
    • USB WiFi Adapter (with certain Realtek chipsets if you want to make it easy on yourself) ($12) (this one from Adafruit works, and this one from Amazon worked for me) (i’ll cover how to setup networking in a future post)

 

Show Me Your Boot (via Serial)

theoretically you should be able to configure networking ahead of time on the microSD and then remote in with just a network connection and power. you could also connect to a display using HDMI-to-DVI or S-Video cables. however, at some point you may need the most basic “fall-back” way to interact with the board (the serial connection), so i’m covering that here.

TIP: these boards can be a little touchy, so it’s best to connect everything while the power is off, then switch it on. i actually plug into a switched power strip to make it easy to turn on/off since there’s no mechanical switch on the board.

  1. insert the microSD card that came with your BBXM (it goes label up towards top of the board, and should click in. it presses again to eject – dont yank it)
  2. attach the USB-to-Serial Cable to the BBXM and to your “host” computer
  3. attach the power cord to the BBXM, but don’t plug it into the wall yet

at this point most computers with a modern OS will work with the USB-to-serial cable without installing any drivers. verify the cable was detected and see what port it was assigned:

  • in Linux (i’m currently using Linux Mint 13 in a virtual machine inside of Windows 8 x64 as my “host” machine):
    • open Terminal, type: ls /dev/ttyUSB* and press enter
    • you should get back at least one listing, usually “/dev/ttyUSB0” (if you have more than one, you’ll have to disconnect the cable, execute the command again and see which one is now missing)
    • if you don’t have a “/dev/ttyUSB#”, Google the lsusb and dmesg commands for more info on troubleshooting
  • on Windows:
    • open Device Manager (right-click on “My Computer”, choose “Manage”, then click on “Device Manager” in the left-side tree of the window that opens).
    • expand the “Ports” section, you should see a “USB-to-Serial” device in the list.
    • at the end of the name should be “COM#”, take note of the number.
serial killa

 

configure a connection to the BBXM:

  • in Linux you can use minicom:
    • use your distro’s package tool to find and install “minicom” (in Mint’s GUI: “Menu” > “Administration” > “Software Manager” > search “minicom” > select it in the results > “Install”)
    • open Terminal, type: sudo minicom -s and press enter
    • goto “Serial Port Setup” and configure:
      • Serial Device: /dev/ttyUSB# (replace # with the correct number you found in the steps above)
      • Bps/Par/Bits: 115200 8N1
      • Hardware Flow Control: Yes
      • Software Flow Control: No
    • press enter to get back to the main menu
    • choose “Save setup as dfl”, then choose “Exit from Minicom”
    • apply power to the BBXM
    • type: sudo minicom and press enter
    • after a second you should see “Initializing Modem”, then a long list of boot status text should scroll by
    • (to exit minicom, press CTRL+A then Z, then X)
mini-me-com

 

  • in Windows you can use putty:
    • download putty.exe from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
    • launch putty and configure a new session:
      • Connection Type: Serial
      • Serial Line: COM# (replace # with the number you noted from Device Manager)
      • Speed: 115200
    • click “Open” and you should get a console window with a blinking cursor
    • apply power to the BBXM
    • you should see boot status text scrolling by
glazing

 

  1. eventually you will get the “Angstrom” ASCII art, and then a “beagleboard login:” prompt. depending on the image that your factory microSD card came with, you may have to wait several minutes the very first time you boot before you get the login prompt – if it looks like it’s hung, give it 5 minutes before you reset.
  2. the login is: root
  3. the password is blank, just press enter
work damn you! oh, well good then!

 

Woopidy Doo, I’m Logged In… Now what?

well, some useful commands for a noob like myself:

  • uname -a
  • reboot (the physical button next to the revision number is also a reset)
  • shutdown now

and what else? you could set it up with a webcam and webserver software to stream images (or something more complex), combine it with an Arduino to make a WiFi controlled robot, host your blog on it, use it to scratch that spot on your back that’s hard to reach…

TIP: the first thing to do is not mess with the factory microSD. put it away as your fail-safe backup, and setup another card as your working drive. it’s very likely the factory card is out of date and you’ll want a newer image anyway. i’ll cover the special format of the card and how to get a newer build in my next post.

war drvr
(awar driver thingyshown above)

 

Self-Study Time Kids

here are some of my “goto” bookmarks for the BBXM:

and some toys:

 

stay tuned for posts on preparing a microSD with an updated build, and getting wired & wireless networking configured…

say something about this post

  • (will not be published)

Comment moderation is enabled. Your comment may take some time to appear.

7 responses to “BeagleBoard-XM: Getting Started (cuz a Raspberry Pi would have been too trendy)”

  1. Avinash Ravi Koushik Reply

    Hey Kris,

    Thanks a lot for the documentation. I am just getting started with the xM & it helped me a lot. Hope I too can write a blog after coming up with an application!!
    (P.S. : Hope you do not mind calling you Kris :) Also can I mail you regarding any doubts? Can I get your mail id ? )

    With regards,
    Avinash

  2. Tanzeel Reply

    i have a problem with beagleboard -xM .
    it is taking to long to boot ,i dont know why …some times it takes half an hour ..but some time it takes upto two hours to boot.
    whan i plug in the 5v DC adapter …a red led (D13) blinks all the way …until it boots properly …but when it boots up it works fine …nothing wrong …but when i shut it down and reboot again ,it again takes that much time to boot …
    can you please help me in this regard .

    thank you so much ..

    • theksmith [website] Reply

      sorry i don’t know, i haven’t been back to play with the BBXM any more as i got onto other projects!

      are you using the stock DC adapter, i know some that don’t provide enough amperage can cause issue… otherise, does it hang on a specific msg during the boot cycle?

      • Bob Dobbs Reply

        Can I just ask, briefly, how did you get wifi setup with the BBXM ? I’ve tried a few different images and some obvious stuff I learned from the BeagleBone Black; however, none of that seems to work with the BBXM.

        • theksmith [website] Reply

          sorry, i haven’t messed with this in so long now that i don’t remember the details. if i ever get back to playing with it then i’ll post an answer for future curious people!

  3. Hammad Reply

    Hi,

    i am facing issue that it is not proceeding next. Below is the messages shown yet and display as well with stopped at 65% loading bar.

    U-Boot 2011.12-00010-ga3eb89c (Jan 29 2012 – 14:53:43)

    OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
    OMAP3 Beagle board + LPDDR/NAND
    I2C: ready
    DRAM: 512 MiB
    NAND: 0 MiB
    MMC: OMAP SD/MMC: 0
    *** Warning – readenv() failed, using default environment

    In: serial
    Out: serial
    Err: serial
    Beagle xM Rev C
    No EEPROM on expansion board
    No EEPROM on expansion board
    Die ID #3d0a00229ff800000163810c13006021
    Net: Net Initialization Skipped
    No ethernet found.
    Hit any key to stop autoboot: 0
    The user button is currently NOT pressed.
    SD/MMC found on device 0
    reading uEnv.txt

    239 bytes read
    Loaded environment from uEnv.txt
    Importing environment from mmc …
    Running uenvcmd …
    Loading file “/boot/uImage” from mmc device 0:2 (xxa2)
    3195484 bytes read
    ## Booting kernel from Legacy Image at 80200000 …
    Image Name: Angstrom/2.6.32/beagleboard
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 3195420 Bytes = 3 MiB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum … OK
    Loading Kernel Image … OK
    OK

    Starting kernel …

    Uncompressing Linux…………………………………………………………………………………..
    [ 0.000000] Linux version 2.6.32 (koen@dominion) (gcc version 4.3.3 (GCC) ) #3 PREEMPT Thu Jan 6 17:37:46 CET 1
    [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    [ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
    [ 0.000000] Machine: OMAP3 Beagle Board
    [ 0.000000] Memory policy: ECC disabled, Data cache writeback
    [ 0.000000] OMAP3630/DM3730 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
    [ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
    [ 0.000000] Reserving 16777216 bytes SDRAM for VRAM
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
    omapdss.def_disp=dvi root=/dev/mmcblk0p2 ro rootfstype=ext3 rootwaitn8
    [ 0.000000] Beagle expansionboard: none
    [ 0.000000] Beagle cameraboard: none
    [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
    [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    [ 0.000000] Memory: 256MB 256MB = 512MB total
    [ 0.000000] Memory: 496256KB available (5900K code, 671K data, 204K init, 0K highmem)
    [ 0.000000] Hierarchical RCU implementation.
    [ 0.000000] NR_IRQS:402
    [ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz
    [ 0.000000] Reprogramming SDRC clock to 400000000 Hz
    [ 0.000000] dpll3_m2_clk rate change failed: -22
    [ 0.000000] GPMC revision 5.0
    [ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
    [ 0.000000] Total of 96 interrupts on 1 active controller
    [ 0.000000] OMAP GPIO hardware version 2.5
    [ 0.000000] OMAP clockevent source: GPTIMER12 at 32768 Hz
    [ 0.000000] Console: colour dummy device 80×30
    [ 0.000000] console [tty0] enabled
    [ 0.000000] Calibrating delay loop… 513.62 BogoMIPS (lpj=2007040)
    [ 0.000000] Mount-cache hash table entries: 512
    [ 0.000000] CPU: Testing write buffer coherency: ok
    [ 0.000000] tmpfs: No value for mount option ‘mode’
    [ 0.000000] devtmpfs: initialized
    [ 0.000000] regulator: core version 0.5
    [ 0.000000] NET: Registered protocol family 16
    [ 0.000000] Found NAND on CS0
    [ 0.000000] Registering NAND on CS0
    [ 0.000000] Unable to get DVI reset GPIO
    [ 0.000000] omap_init_mbox: platform not supported
    [ 0.000000] Target VDD1 OPP = 4, VDD2 OPP = 2
    [ 6.972351] OMAP DMA hardware revision 5.0
    [ 6.978454] bio: create slab at 0
    [ 6.979675] SCSI subsystem initialized
    [ 6.980957] usbcore: registered new interface driver usbfs
    [ 6.981140] usbcore: registered new interface driver hub
    [ 6.981323] usbcore: registered new device driver usb
    [ 6.981689] i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz
    [ 6.984375] twl4030: PIH (irq 7) chaining IRQs 368..375
    [ 6.984436] twl4030: power (irq 373) chaining IRQs 376..383
    [ 6.984710] twl4030: gpio (irq 368) chaining IRQs 384..401
    [ 6.986389] regulator: VUSB1V5: 1500 mV normal standby
    [ 6.986633] regulator: VUSB1V8: 1800 mV normal standby
    [ 6.986877] regulator: VUSB3V1: 3100 mV normal standby
    [ 6.990417] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
    [ 6.990814] regulator: VMMC1: 1850 3150 mV normal standby
    [ 6.991088] regulator: VDAC: 1800 mV normal standby
    [ 6.991333] regulator: VPLL2: 1800 mV normal standby
    [ 6.991577] regulator: VSIM: 1800 3000 mV normal standby
    [ 6.991943] regulator: VAUX3: 1800 mV normal standby
    [ 6.992309] regulator: VAUX4: 1800 mV normal standby
    [ 6.992462] i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz
    [ 7.002075] i2c_omap i2c_omap.3: bus 3 rev4.0 at 100 kHz
    [ 7.003234] Switching to clocksource 32k_counter
    [ 7.012023] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
    [ 7.012329] musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
    [ 7.012359] musb_hdrc musb_hdrc: MUSB HDRC host driver
    [ 7.012512] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
    [ 7.012664] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [ 7.012695] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [ 7.012756] usb usb1: Product: MUSB HDRC host driver
    [ 7.012786] usb usb1: Manufacturer: Linux 2.6.32 musb-hcd
    [ 7.012817] usb usb1: SerialNumber: musb_hdrc
    [ 7.013427] hub 1-0:1.0: USB hub found
    [ 7.013488] hub 1-0:1.0: 1 port detected
    [ 7.014526] NET: Registered protocol family 2
    [ 7.014770] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
    [ 7.015319] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
    [ 7.015747] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
    [ 7.015991] TCP: Hash tables configured (established 16384 bind 16384)
    [ 7.016021] TCP reno registered
    [ 7.016052] UDP hash table entries: 256 (order: 0, 4096 bytes)
    [ 7.016113] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    [ 7.016357] NET: Registered protocol family 1
    [ 7.016784] RPC: Registered udp transport module.
    [ 7.016815] RPC: Registered tcp transport module.
    [ 7.016845] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [ 7.017700] omap-iommu omap-iommu.0: isp registered
    [ 7.019500] VFS: Disk quotas dquot_6.5.2
    [ 7.019622] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    [ 7.020690] squashfs: version 4.0 (2009/01/31) Phillip Lougher
    [ 7.021484] JFFS2 version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.
    [ 7.022308] msgmni has been set to 969
    [ 7.025817] alg: No test for stdrng (krng)
    [ 7.026123] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    [ 7.026184] io scheduler noop registered
    [ 7.026214] io scheduler deadline registered
    [ 7.026367] io scheduler cfq registered (default)
    [ 7.089447] OMAP DSS rev 2.0
    [ 7.089538] OMAP DISPC rev 3.0
    [ 7.089599] OMAP VENC rev 2
    [ 7.089843] OMAP DSI rev 1.0
    [ 7.426239] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    [ 7.444549] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
    [ 7.462249] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
    [ 7.479919] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
    [ 8.056091] console [ttyS2] enabled
    [ 8.066162] brd: module loaded
    [ 8.072357] loop: module loaded
    [ 8.076690] omap2-nand driver initializing
    [ 8.081115] No NAND device found!!!
    [ 8.084838] No NAND device found!!!
    [ 8.089355] usbcore: registered new interface driver catc
    [ 8.094818] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
    [ 8.100891] usbcore: registered new interface driver kaweth
    [ 8.106567] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
    [ 8.114227] usbcore: registered new interface driver pegasus
    [ 8.119934] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver
    [ 8.126983] usbcore: registered new interface driver rtl8150
    [ 8.132781] usbcore: registered new interface driver asix
    [ 8.138336] usbcore: registered new interface driver cdc_ether
    [ 8.144317] usbcore: registered new interface driver dm9601
    [ 8.150024] usbcore: registered new interface driver smsc95xx
    [ 8.155914] usbcore: registered new interface driver gl620a
    [ 8.161651] usbcore: registered new interface driver net1080
    [ 8.167449] usbcore: registered new interface driver plusb
    [ 8.173065] usbcore: registered new interface driver rndis_host
    [ 8.179138] usbcore: registered new interface driver cdc_subset
    [ 8.185211] usbcore: registered new interface driver zaurus
    [ 8.190948] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
    [ 8.199035] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
    [ 8.205871] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
    [ 8.211883] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2
    [ 8.219512] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
    [ 8.237762] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
    [ 8.243682] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    [ 8.250549] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [ 8.257873] usb usb2: Product: OMAP-EHCI Host Controller
    [ 8.263275] usb usb2: Manufacturer: Linux 2.6.32 ehci_hcd
    [ 8.268707] usb usb2: SerialNumber: ehci-omap.0
    [ 8.273956] hub 2-0:1.0: USB hub found
    [ 8.277801] hub 2-0:1.0: 3 ports detected
    [ 8.308197] Initializing USB Mass Storage driver…
    [ 8.313262] usbcore: registered new interface driver usb-storage
    [ 8.319366] USB Mass Storage support registered.
    [ 8.324401] mice: PS/2 mouse device common for all mice
    [ 8.330047] input: gpio-keys as /devices/platform/gpio-keys/input/input0
    [ 8.337829] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/inpu1
    [ 8.348541] i2c /dev entries driver
    [ 8.352630] Linux video capture interface: v2.00
    [ 8.357604] omap-iommu omap-iommu.0: isp: version 1.1
    [ 8.363952] vpfe_init
    [ 8.366821] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
    [ 8.480224] mmci-omap-hs mmci-omap-hs.1: err -16 configuring card detect
    [ 8.487274] Registered led device: beagleboard::usr0
    [ 8.492462] Registered led device: beagleboard::usr1
    [ 8.499084] Registered led device: beagleboard::pmu_stat
    [ 8.506164] usbcore: registered new interface driver usbhid
    [ 8.511840] usbhid: USB HID core driver
    [ 8.515899] Advanced Linux Sound Architecture Driver Version 1.0.21.
    [ 8.522796] usbcore: registered new interface driver snd-usb-audio
    [ 8.606323] No device for DAI omap-mcbsp-dai-0
    [ 8.610839] No device for DAI omap-mcbsp-dai-1
    [ 8.615356] No device for DAI omap-mcbsp-dai-2
    [ 8.619842] No device for DAI omap-mcbsp-dai-3
    [ 8.624359] No device for DAI omap-mcbsp-dai-4
    [ 8.628875] OMAP3 Beagle SoC init
    [ 8.632965] asoc: twl4030 omap-mcbsp-dai-0 mapping ok
    [ 8.644409] ALSA device list:
    [ 8.647430] #0: omap3beagle (twl4030)
    [ 8.651397] oprofile: using arm/armv7
    [ 8.655334] TCP cubic registered
    [ 8.658599] NET: Registered protocol family 17
    [ 8.663146] NET: Registered protocol family 15
    [ 8.667755] lib80211: common routines for IEEE802.11 drivers
    [ 8.673492] ThumbEE CPU extension supported.
    [ 8.677825] Power Management for TI OMAP3.
    [ 8.683135] Unable to set L3 frequency (400000000)
    [ 8.688018] Switched to new clocking rate (Crystal/Core/MPU): 26.0/400/1000 MHz
    [ 8.695404] IVA2 clocking rate: 800 MHz
    [ 8.870605] SmartReflex driver initialized
    [ 8.874816] omap3beaglelmb: Driver registration complete
    [ 8.885375] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    [ 8.893646] registered taskstats version 1
    [ 9.003936] Console: switching to colour frame buffer device 160×45
    [ 9.026092] regulator_init_complete: incomplete constraints, leaving VAUX3 on
    [ 9.033905] regulator_init_complete: incomplete constraints, leaving VDAC on
    [ 9.041320] omap_vout omap_vout: probed for an unknown device
    [ 9.047576] Waiting for root device /dev/mmcblk0p2…
    [ 9.073791] mmc0: new high speed SDHC card at address 1234
    [ 9.079711] mmcblk0: mmc0:1234 SA08G 7.28 GiB
    [ 9.084533] mmcblk0: p1 p2
    [ 9.163574] EXT3-fs (mmcblk0p2): recovery required on readonly filesystem
    [ 9.170654] EXT3-fs (mmcblk0p2): write access will be enabled during recovery
    [ 9.181030] EXT3-fs (mmcblk0p2): recovery complete
    [ 9.186065] kjournald starting. Commit interval 5 seconds
    [ 9.925262] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    [ 9.936035] VFS: Mounted root (ext3 filesystem) readonly on device 179:2.
    [ 9.949401] devtmpfs: mounted
    [ 9.955963] Freeing init memory: 204K
    INIT: version 2.86 booting
    Please wait: booting…
    Starting udev
    /etc/rcS.d/S03udev: line 50: can’t create /tmp/uname: Read-only file system
    touch: /tmp/uname: Read-only file system
    Remounting root file system…
    [ 10.525329] EXT3-fs (mmcblk0p2): using internal journal
    Caching udev devnodes
    Populating dev cachemv: cannot rename ‘/tmp/uname’: No such file or directory
    [ 11.353881] Bluetooth: Core ver 2.15
    [ 11.357727] NET: Registered protocol family 31
    [ 11.362213] Bluetooth: HCI device and connection manager initialized
    [ 11.368652] Bluetooth: HCI socket layer initialized
    [ 11.387908] Bluetooth: L2CAP ver 2.14
    [ 11.391601] Bluetooth: L2CAP socket layer initialized
    [ 11.410766] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    [ 11.518493] NET: Registered protocol family 10
    [ 11.549835] Bluetooth: RFCOMM TTY layer initialized
    [ 11.554870] Bluetooth: RFCOMM socket layer initialized
    [ 11.560058] Bluetooth: RFCOMM ver 1.11
    ALSA: Restoring mixer settings…
    Configuring network interfaces… /usr/sbin/alsactl: load_state:1610: No soundcards found…
    ifconfig: SIOCGIFFLAGS: No such device
    ifconfig: SIOCGIFFLAGS: No such device
    eth0 No such device

    ifconfig: SIOCGIFFLAGS: No such device
    ifconfig: SIOCGIFFLAGS: No such device
    ifconfig: SIOCGIFFLAGS: No such device
    usb0 No such device

    ifconfig: SIOCGIFFLAGS: No such device
    done.
    Starting portmap daemon: portmapportmap: fork: No such device.
    net.ipv4.conf.default.rp_filter = 1
    net.ipv4.conf.all.rp_filter = 1
    hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
    Tue Jan 11 10:13:00 GMT 2011
    hwclock: can’t open ‘/dev/misc/rtc’: No such file or directory
    [ 54.320953] CMEMK module: built on Jan 2 2011 at 09:59:00
    [ 54.326812] Reference Linux version 2.6.32
    [ 54.331115] File /OE/angstrom-dev/work/beagleboard-angstrom-linux-gnueabi/ti-linuxutils-1_2_25_05_11-r97d/lic
    [ 54.347778] CMEM Range Overlaps Kernel Physical – allowing overlap
    [ 54.354003] CMEM phys_start (0x86300000) overlaps kernel (0x80000000 -> 0xa0000000)
    [ 54.361968] CMEMK Error: Failed to request_mem_region(0x86300000, 16777216)
    [ 54.395477] DSPLINK Module (1.65.00.03) created on Date: Jan 4 2011 Time: 14:20:12
    [ 54.425262] SDMAK module: built on Jan 2 2011 at 09:59:08
    [ 54.430786] Reference Linux version 2.6.32
    [ 54.435455] File /OE/angstrom-dev/work/beagleboard-angstrom-linux-gnueabi/ti-linuxutils-1_2_25_05_11-r97d/lic

    is there any issue or it will take time. accordingly i have got some rtc messages as well. kindly help me out as i am new and booting this first time.

    Thanks,

    Hammad