• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 280 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Beagleboard XM driver error

Andre aleksandrov
Prodigy 30 points

I am trying to create a USB sniffer out of the Beagleboard XM. I am following the instructions given in this link. http://www.elinux.org/BeagleBoard/GSoC/USBSniffer Unfortunately, I am having problems. I have tried to email the developer from the link but he has not responded. I was wondering if you guys could help. When I run the command, this is what i get.

root@beagleboard:~/arm# ./sniff
List of devices:
1-2.1: Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
====
Choose the device to sniff [default:1-2.1]:
Chosen FIFO configuration: ep1in:1024,ep2out:1024,ep3in:32
[  173.951873] usb0: unregister 'smsc95xx' usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet
Device unbound!
[  174.235321] musb_hdrc: Unknown parameter `fifo_config'
FATAL: Error inserting musb_hdrc (/lib/modules/2.6.32-usbsniffer/kernel/drivers/usb/musb/musb_hdrc.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Starting tcpdump
mv: cannot stat `/media/ram/dump': No such file or directory
tcpdump: error while loading shared libraries: libnl.so.1: cannot open shared object file: No such file or directory
Loading proxy driver...
[  175.296478] musb_hdrc: version 6.0, musb-dma, peripheral, debug=0
[  175.303619] musb_hdrc: USB Peripheral mode controller at fa0ab000 using DMA, IRQ 92
[  175.324707] Proxy Gadget: Proxy Gadget, version: 2010 ... debug=0
[  175.330932] Proxy Gadget: device_probe (0424:ec00)
[  175.336669] Proxy Gadget: Attaching!
[  175.340759] Proxy Gadget: Using high speed.
[  175.344970] Proxy Gadget: using musb_hdrc
[  175.350769] usbcore: registered new device driver proxy
Device should work now...
Device should work now...
Device should work now...
Device should work now...
Press enter to stop logging, and reload g_ether

What i cannot understand is why i am getting FATAL: Error inserting musb_hdrc ... Unknown symbol in module, or unknown parameter (see dmesg)
I followed the instructions. One thing that i did not do is Install libpcap-1.1.1 and tcpdump-4.1.1 from source. What i did was run these two commands on the BB XM.

opkg install libpcap

opkg install tcpdump

Other than that i did exactly what the page said.

  • 0
    Prodigy 30 points

    I think I know where things are going haywire. Maybe a little explanation might help. I created a filesystem/u-boot/MLO/kernel using Narcissus online image builder. The image boots up great. I have zero problems. However I am required to use a different kernel because I am going to be using a custom driver. The kernel builds without any problems. The problem starts when I copy my compiled kernel to the image built by Narcissus. The board still boots up fine…even my kernel. The problem seems to be that when I boot up a message says that my filesystem is read only and hence I cannot write anything to the image. I don’t understand why. When I run the image with the original Narcissus kernel, I do have write permissions.