3 ms·
Got mine couple of days back and here are a few tips: - The default OS version had some issues that I was not able to ssh into the board. Once I downloaded and
by krishna2 13y ago
Got mine couple of days back and here are a few tips:
- The default OS version had some issues that I was not able to ssh into the board. Once I downloaded and loaded the latest version available on the site, I was able to ssh as root.
- I was not able to connect serially (from my mac). Turns out that the FTDI driver they provide is 32 bit but (my) Mac needs a 64 bit. So you have to install the 32 bit, save the Info.plist, then install the 64 bit and copy it back and chmod permissions correctly.
- While trying to do a "opkg upgrade", be careful. Mine got into some issues installing a downloaded version half way through the process. But this also somehow broke the network connection. So no more updates. I almost thought I bricked my board. But I was able to again use my SD (from the previous downloaded latest version) to the rescue and bring it back to life again.
- gardarh 13y agoAlso there is a nice Ubuntu port available. It feels rather stable and more familiar than Angstrom, I recommend it. Of course you'll lose Cloud9 from the box.
- krishna2 13y agoYes, I am planning to go Ubuntu as well.
- mintyfresh 13y agoI had the same issue not being able to ssh into the shipped OS. While updating to the latest OS, I ran into similar issues writing the latest version to the eMMC memory and also thought I bricked my board. The external SD port and the eMMC Flasher images really are a "get out of jail free card." This board is a beautiful little piece of hardware. I'm really looking forward to tinkering around with it.
- peddamat 13y agoWow, ordered on Friday, received today, with the standard shipping option. Digikey rocks! After reading this post, I thought I would be clever and just install the proper drivers, turns out, you do have to follow krishna2's instructions exactly. Hopefully this saves others the slight headache, I went through: - Install the HoRNDIS-rel4.pkg network drivers included on the board. - Install the FTDI_Ser.dmg serial drivers included on the board. When I installed them, an error message popped up stating something about the OS being unable to use the driver. - Download the 64-bit drivers here: http://www.ftdichip.com/Drivers/VCP.htm http://www.ftdichip.com/Drivers/VCP.htm . As of this posting, this is the latest version: http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriver_v2_2_18.dmg http://www.ftdichip.com/Drivers/VCP/MacOSX/FTDIUSBSerialDriv... - Before installing the latest serial drivers: cp /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist /tmp - Install the new drivers. - cp /tmp/Info.plist /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist - Enjoy! Here's the error message, for SEO juice: USBMSC Identifier (non-unique): 5A-1813BBBK0554 0x1d6b 0x104 0x308 HoRNDIS: init: HoRNDIS tethering driver for Snow Leopard+, by Joshua Wise 0 0 dgmdmcontrol: start - Failed to find the CDC driver HoRNDIS: rndisInit: their MTU 1486 HoRNDIS: init: starting up with MTU 1486 HoRNDISUSBInterface: Ethernet address c8:a0:30:ab:92:29 0 0 AppleUSBCDCACMData: start - allocateResources failed 0 1 AppleUSBCDCECMData: start - Find CDC driver for ECM data interface failed 0 0 dgmdmcontrol: start - Failed to find the CDC driver 0 [Level 5] [com.apple.message.domain com.apple.commssw.cdc.device] [com.apple.message.driver AppleUSBCDCACMData] [com.apple.message.vendor_id 0x1D6B] [com.apple.message.product_id 0x104] AppleUSBCDCACMData: Version number - 4.1.23, Input buffers 8, Output buffers 16 HoRNDIS: rndisCommand: unsupported: RNDIS_MSG_INDICATE AppleUSBCDC: Version number - 4.1.23 Sandbox: sandboxd(36667) deny mach-lookup com.apple.coresymbolicationd Kext com.FTDI.driver.FTDIUSBSerialDriver not found for unload request. Kext com.FTDI.driver.FTDIUSBSerialDriver not found for unload request.