Hello USB group.
I downloaded the source for 2.6.35-22-generic, applied the relevant patch
which adds sam-ba.c, modifies Kconfig and adds a new sam-ba target in the Makefile.
I updated the .config file to include the sam-ba module and performed the
following build steps from ./linux-headers-2.6.35-22-generic:
make oldconfig
make prepare
This created the new sam-ba.ko module.
make M=drivers/usb/serial
I then run the following (from a directory containing sam-ba.ko):
sudo modprobe usbserial vendor=0x03eb product=0x6124
lsusb -d 03eb:6124
sudo insmod sam-ba
Edited output from lsmod gives:
linux_box@bbb:/data/work/sam7/sam-ba_cdc_linux$ lsmod
Module Size Used by
sam_ba 2810 0
usbserial 32846 1 sam_ba
Nov 18 12:47:43 nbryan kernel: [ 758.747594] usbcore: registered new interface driver usbserial
Nov 18 12:47:43 nbryan kernel: [ 758.747653] USB Serial support registered for generic
Nov 18 12:47:43 nbryan kernel: [ 758.747726] usbcore: registered new interface driver usbserial_generic
Nov 18 12:47:43 nbryan kernel: [ 758.747734] usbserial: USB Serial Driver core
Nov 18 12:47:43 nbryan kernel: [ 759.163181] USB Serial support registered for sam-ba
Nov 18 12:47:43 nbryan kernel: [ 759.163258] usbcore: registered new interface driver sam-ba
Nov 18 12:47:43 nbryan kernel: [ 759.163265] sam_ba: v1.0: Atmel SAM Boot Assistant (SAM-BA) driver
Connecting the AT91SAM7X board gives the following output from dmesg:
Nov 18 12:49:11 nbryan kernel: [ 846.536062] usb 3-2: new full speed USB device using uhci_hcd and address 3
Nov 18 12:49:11 nbryan kernel: [ 846.696296] usbserial_generic 3-2:1.0: Generic device with no bulk out, not allowed.
Nov 18 12:49:11 nbryan kernel: [ 846.696321] usbserial_generic: probe of 3-2:1.0 failed with error -5
Nov 18 12:49:11 nbryan kernel: [ 846.696482] usbserial_generic 3-2:1.1: sam-ba converter detected
Nov 18 12:49:11 nbryan kernel: [ 846.696829] usb 3-2: sam-ba converter now attached to ttyUSB0
Now using SAM-BA 2.10 I see:
-I- Waiting ...
-I- TCL platform : Linux
-I- SAM-BA CDC 2.10 on : linux
-I- Connection : /dev/ttyUSB0 (target(comType) = 3)
-I- Board : at91sam7x256-ek
-I- Traces Level : 4
-I- target(handle) : file5
Read device Chip ID at 0xfffff240 --- get 0x271b0940
-I- Found processor : at91sam7xc256 (Chip ID : 0x271b0940)
Read device Chip ID at 0xffffee40 --- get 0x00000000
followed by a communication error pop-up.
The first time when I built this I did successfully communicate with the
bootloader, but not since.
Now, I suspect my method of using 'insmod' is not ideal. Does anyone
see a problem with the way that I have tried to use the new sam-ba module?
Thanks,
Neil.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
