Kernel messages overflowing on the BBB

The USB gadget support build into the latest Angstrom kernel (as of the 6-6-2013 version), had debugging enabled in it's configuration.  This causes the following 7 messages to repeat in the logs:

[ 8732.441147] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER
[ 8732.444806]  gadget: rndis reqa1.01 v0000 i0000 l4096
[ 8732.445090]  gadget: rndis req21.00 v0000 i0000 l36
[ 8732.448797]  gadget: rndis reqa1.01 v0000 i0000 l4096
[ 8732.449226]  gadget: rndis req21.00 v0000 i0000 l36
[ 8732.452790]  gadget: rndis reqa1.01 v0000 i0000 l4096
[ 8732.453162]  gadget: rndis req21.00 v0000 i0000 l36
This "SPAM" makes the log nearly unusable if you are watching for something else important.

The particular configuration item is:  CONFIG_USB_GADGET_DEBUG=y

Robert Nelson confirms my suspicion here (eewiki.net) and indicates that the next build will have this configuration changed.

I am not aware of any way to correct this short of rebuilding the kernel.  I think I can wait for Robert...  :-)

BeagleBone Black Progress Notes

The BBB is fairly new, the tools and software are a work in progress.  It's easy to get distracted chasing down a problem or feature that I want to make work, and forget what I have done or plan on working on next.  

GOALS

CONNECTIVITY

• Console port, Serial
• USB port to Host, SSH via Gadget Ethernet
• USB Internet from Host to BBB
• Direct Ethernet port to BBB
• WiFi

I2C

• Wire LED display (Adafruit I2C backpack 7 Segment Display)
• Validate via command line
• Install I2C library for JavaScript environment
• Validate connectivity thru library
• Create library for display

NODE

• Create Node app to update LED display

Turns out that order very much matters, and it's pretty easy to get sucked into a side task and loose track.

PROCESS

1. Download and install updated Angstrom Image (2013-6-6 eMMC flasher image) via card.

2. Configure Windows 7 USB Internet Sharing (see blog entry)

3. Update System

4. Test I2C from Command Line

5. Configure NPM

6. Install I2C Node Module

Updating BeagleBone Black System

These commands update the BeagleBone Black system files. 

Remember to replace the kernel version number show with an 'x', with the one shown during the upgrade.  This forces the kernel upgrade to occur.  If not done, you can lock up the BBB causing a rewrite of the eMMC to be required.

opkg update
opkg upgrade
opkg --force-overwrite install kernel-image-3.8.x

Node Package Manager (NPM)

It took me a while to determine that I had to configure NPM to not care about SSL Certificates.  Until then, when I was trying to install a package, I would get Cert CA errors.  Use this:

npm config set strict-ssl false

I also discovered that installing certain packages failed with messages indicating python problems.  I suspect that the Angstrom image doesn't have all the necessary dependencies for NPM installed.  Use this to get NPM working smoothly:

opkg update
opkg install python-modules
opkg install task-native-sdk

Console (Debugging) Cable from AdaFruit.com

I am using this cable to connect to the BeagleBone Black. 
Though not technically required for operation, it is helpful and will be nearly required as I start working with changing the Linux kernel.

http://www.adafruit.com/products/954

 

Here is how it is connected:

Board     Wire      Function
Pin 1      Black      Ground
Pin 4      Green     Receive
Pin 5      White     Transmit

The default serial port settings for the board are:
Baud 115,200
Bits 8
Parity N
Stop Bits 1
Handshake None

I use PUTTY as a Windows terminal program.  http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Beaglebone Black - Embedded Linux Device

Just started working with a BeagleBone Black. 
Initial impression is very good.
I hope to document my progress here.

http://adafruit.com/products/1278