svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Compute module not talking

Sat Jul 26, 2014 9:28 am

I cannot get the Compute module (in its IO board) to listen properly.

The documentation is quite poor and gives no hints about troubleshooting. I don't have to reboot the Compute module to get it to appear as a mass storage device do I?

Code: Select all

[Boot up Raspberry Pi into Linux on a larger (8GB) SD card]
$ lsblk
NAME        MAJ:MIN RM  SIZE  RO  TYPE  MOUNTPOINT
mmcblk0     179:0    0  7.4G   0  disk 
|-mmcblk0p1 179:1    0   56M   0  part  /boot
|-mmcblk0p2 179:2    0  7.4G   0  part  /
$sudo ./rpiboot
Waiting for BCM2835 ...
[Boot up Compute module, jumper set to slave USB, USB lead connected]
Found serial - 0: writing file usbbootcode.bin
Successful
Waiting for BCM2835 ...
Found serial - 1: writing file msd.bin
Successful
Raspberry Pi is now a mass storage device, use lsblk to find it.
$ lsblk
NAME        MAJ:MIN RM  SIZE  RO  TYPE  MOUNTPOINT
mmcblk0     179:0    0  7.4G   0  disk 
|-mmcblk0p1 179:1    0   56M   0  part  /boot
|-mmcblk0p2 179:2    0  7.4G   0  part  /
$

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Sat Jul 26, 2014 5:48 pm

Hmmm, that's odd :?
I've just tried the same on my Pi (previously I'd only run rpiboot on my desktop PC) and I get

Code: Select all

$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk0     179:0    0   7.4G  0 disk 
├─mmcblk0p1 179:1    0    56M  0 part /boot
└─mmcblk0p2 179:2    0   2.7G  0 part /
$ sudo ./rpiboot 
Waiting for BCM2835 ...
Found serial = 0: writing file usbbootcode.bin
Successful
Waiting for BCM2835 ...
Found serial = 1: writing file msd.bin
Successful
Raspberry Pi is now a mass storage device, use lsblk to find it
$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    1   3.7G  0 disk 
├─sda1        8:1    1    56M  0 part 
└─sda2        8:2    1   2.7G  0 part 
mmcblk0     179:0    0   7.4G  0 disk 
├─mmcblk0p1 179:1    0    56M  0 part /boot
└─mmcblk0p2 179:2    0   2.7G  0 part /
(I haven't expanded either rootfs yet, which is why mmcblk0p2 and sda2 only show up as only 2.7G)

What output do you get from dmesg ?

svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Re: Compute module not talking

Sat Jul 26, 2014 6:51 pm

What output do you get from dmesg?
I hope it means more to you than me!

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.12.22+ (dc4@dc4-arm-01) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08) ) #691 PREEMPT Wed Jun 18 18:29:58 BST 2014
[    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine: BCM2708
[    0.000000] cma: CMA: reserved 8 MiB at 1b800000
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 114688
[    0.000000] free_area_init_node: node 0, pgdat c05fcdf0, node_mem_map c06ae000
[    0.000000]   Normal zone: 896 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 114688 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113792
[    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708.boardrev=0xf bcm2708.serial=0x7045ac9 smsc95xx.macaddr=B8:27:EB:04:5A:C9 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
[    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: 439664K/458752K available (4376K kernel code, 238K rwdata, 1340K rodata, 143K init, 701K bss, 19088K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdc800000 - 0xff000000   ( 552 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc059d54c   (5718 kB)
[    0.000000]       .init : 0xc059e000 - 0xc05c1ee4   ( 144 kB)
[    0.000000]       .data : 0xc05c2000 - 0xc05fd900   ( 239 kB)
[    0.000000]        .bss : 0xc05fd90c - 0xc06ad0f8   ( 702 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:394
[    0.000000] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967ms
[    0.000000] Switching to timer-based delay loop
[    0.000000] Console: colour dummy device 80x30
[    0.000000] console [tty1] enabled
[    0.001264] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)
[    0.001325] pid_max: default: 32768 minimum: 301
[    0.001819] Mount-cache hash table entries: 512
[    0.002648] Initializing cgroup subsys memory
[    0.002757] Initializing cgroup subsys devices
[    0.002795] Initializing cgroup subsys freezer
[    0.002829] Initializing cgroup subsys blkio
[    0.002971] CPU: Testing write buffer coherency: ok
[    0.003428] Setting up static identity map for 0xc0427670 - 0xc04276cc
[    0.005343] devtmpfs: initialized
[    0.022006] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[    0.023593] NET: Registered protocol family 16
[    0.028954] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[    0.029633] cpuidle: using governor ladder
[    0.029679] cpuidle: using governor menu
[    0.030277] bcm2708.uart_clock = 0
[    0.032098] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.032152] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.032190] mailbox: Broadcom VideoCore Mailbox driver
[    0.032291] bcm2708_vcio: mailbox at f200b880
[    0.032398] bcm_power: Broadcom power driver
[    0.032436] bcm_power_open() -> 0
[    0.032462] bcm_power_request(0, 8)
[    0.533183] bcm_mailbox_read -> 00000080, 0
[    0.533222] bcm_power_request -> 0
[    0.533453] Serial: AMBA PL011 UART driver
[    0.533624] dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83, base_baud = 0) is a PL011 rev3
[    0.891952] console [ttyAMA0] enabled
[    0.918834] bio: create slab <bio-0> at 0
[    0.924351] SCSI subsystem initialized
[    0.928346] usbcore: registered new interface driver usbfs
[    0.934048] usbcore: registered new interface driver hub
[    0.939615] usbcore: registered new device driver usb
[    0.946243] Switched to clocksource stc
[    0.950501] FS-Cache: Loaded
[    0.953653] CacheFiles: Loaded
[    0.969362] NET: Registered protocol family 2
[    0.974861] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.982263] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.988834] TCP: Hash tables configured (established 4096 bind 4096)
[    0.995285] TCP: reno registered
[    0.998583] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    1.004454] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    1.011208] NET: Registered protocol family 1
[    1.016128] RPC: Registered named UNIX socket transport module.
[    1.022183] RPC: Registered udp transport module.
[    1.026944] RPC: Registered tcp transport module.
[    1.031663] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.039040] bcm2708_dma: DMA manager at f2007000
[    1.043780] bcm2708_gpio: bcm2708_gpio_probe c05cfed0
[    1.049344] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[    1.058957] audit: initializing netlink socket (disabled)
[    1.064458] type=2000 audit(0.910:1): initialized
[    1.230586] VFS: Disk quotas dquot_6.5.2
[    1.234857] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.243856] FS-Cache: Netfs 'nfs' registered for caching
[    1.250813] NFS: Registering the id_resolver key type
[    1.255983] Key type id_resolver registered
[    1.260300] Key type id_legacy registered
[    1.265075] msgmni has been set to 874
[    1.270882] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    1.278741] io scheduler noop registered
[    1.282694] io scheduler deadline registered (default)
[    1.288291] io scheduler cfq registered
[    1.293456] BCM2708FB: allocated DMA memory 5bc00000
[    1.298638] BCM2708FB: allocated DMA channel 0 @ f2007000
[    1.338753] Console: switching to colour frame buffer device 240x67
[    1.361499] uart-pl011 dev:f1: no DMA platform data
[    1.367239] vc-cma: Videocore CMA driver
[    1.371262] vc-cma: vc_cma_base      = 0x00000000
[    1.376044] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
[    1.381607] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
[    1.396961] brd: module loaded
[    1.405551] loop: module loaded
[    1.409184] vchiq: vchiq_init_state: slot_zero = 0xdb800000, is_master = 0
[    1.417320] Loading iSCSI transport class v2.0-870.
[    1.423489] usbcore: registered new interface driver smsc95xx
[    1.429708] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    1.635807] Core Release: 2.80a
[    1.639143] Setting default values for core params
[    1.644069] Finished setting default values for core params
[    1.849854] Using Buffer DMA mode
[    1.853259] Periodic Transfer Interrupt Enhancement - disabled
[    1.859231] Multiprocessor Interrupt Enhancement - disabled
[    1.864915] OTG VER PARAM: 0, OTG VER FLAG: 0
[    1.869395] Dedicated Tx FIFOs mode
[    1.873320] WARN::dwc_otg_hcd_init:1042: FIQ DMA bounce buffers: virt = 0xdbc14000 dma = 0x5bc14000 len=9024
[    1.883402] FIQ FSM acceleration enabled for :
[    1.883402] Non-periodic Split Transactions
[    1.883402] Periodic Split Transactions
[    1.883402] High-Speed Isochronous Endpoints
[    1.900473] dwc_otg: Microframe scheduler enabled
[    1.900566] WARN::hcd_init:473: FIQ at 0xc03080cc
[    1.905375] WARN::hcd_init:474: FIQ ASM at 0xc0308348 length 36
[    1.911470] WARN::hcd_init:500: MPHI regs_base at 0xdc806000
[    1.917295] dwc_otg bcm2708_usb: DWC OTG Controller
[    1.922315] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
[    1.929763] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
[    1.935382] Init: Port Power? op_state=1
[    1.939426] Init: Power Port (0)
[    1.947799] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.959419] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.971418] usb usb1: Product: DWC OTG Controller
[    1.980853] usb usb1: Manufacturer: Linux 3.12.22+ dwc_otg_hcd
[    1.991429] usb usb1: SerialNumber: bcm2708_usb
[    2.001609] hub 1-0:1.0: USB hub found
[    2.010276] hub 1-0:1.0: 1 port detected
[    2.019541] dwc_otg: FIQ enabled
[    2.019559] dwc_otg: NAK holdoff enabled
[    2.019569] dwc_otg: FIQ split-transaction FSM enabled
[    2.019590] Module dwc_common_port init
[    2.020064] usbcore: registered new interface driver usb-storage
[    2.031407] mousedev: PS/2 mouse device common for all mice
[    2.042531] bcm2835-cpufreq: min=700000 max=700000 cur=700000
[    2.053336] bcm2835-cpufreq: switching to governor powersave
[    2.063828] bcm2835-cpufreq: switching to governor powersave
[    2.074344] sdhci: Secure Digital Host Controller Interface driver
[    2.085250] sdhci: Copyright(c) Pierre Ossman
[    2.094333] sdhci: Enable low-latency mode
[    2.146318] mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMA
[    2.159175] mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77
[    2.170022] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.182537] ledtrig-cpu: registered to indicate activity on CPUs
[    2.200787] hidraw: raw HID events driver (C) Jiri Kosina
[    2.211313] usbcore: registered new interface driver usbhid
[    2.223995] Indeed it is in host mode hprt0 = 00021501
[    2.236039] usbhid: USB HID core driver
[    2.249718] TCP: cubic registered
[    2.276279] Initializing XFRM netlink socket
[    2.285251] NET: Registered protocol family 17
[    2.316547] Key type dns_resolver registered
[    2.347619] registered taskstats version 1
[    2.377449] Waiting for root device /dev/mmcblk0p2...
[    2.406639] mmc0: read SD Status register (SSR) after 5 attempts
[    2.427058] mmc0: new high speed SDHC card at address e624
[    2.438027] mmcblk0: mmc0:e624 SU08G 7.40 GiB 
[    2.449241]  mmcblk0: p1 p2
[    2.516495] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    2.529432] Indeed it is in host mode hprt0 = 00001101
[    2.746722] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
[    2.758725] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.775704] hub 1-1:1.0: USB hub found
[    2.785913] hub 1-1:1.0: 3 ports detected
[    2.866495] EXT4-fs (mmcblk0p2): recovery complete
[    2.878140] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.891218] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.903979] devtmpfs: mounted
[    2.912389] Freeing unused kernel memory: 140K (c059e000 - c05c1000)
[    3.076484] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    3.186797] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.199323] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.216580] smsc95xx v1.0.4
[    3.292686] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:04:5a:c9
[    3.386569] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[    3.505702] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c52e
[    3.529602] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.543749] usb 1-1.3: Product: USB Receiver
[    3.553361] usb 1-1.3: Manufacturer: Logitech
[    3.580112] input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/input/input0
[    3.600391] hid-generic 0003:046D:C52E.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input0
[    3.650288] input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.1/input/input1
[    3.669635] hid-generic 0003:046D:C52E.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input1
[    4.663157] udevd[156]: starting version 175
[    6.957808] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
[   11.067615] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   11.617191] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   18.042898] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   20.969401] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   22.572871] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   26.322474] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFS
[   74.403035] usb 1-1.2: new full-speed USB device number 5 using dwc_otg
[   74.512958] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=2763
[   74.512991] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   74.513008] usb 1-1.2: Product: BCM2708 Boot
[   74.513022] usb 1-1.2: Manufacturer: Broadcom
[   76.469255] usb 1-1.2: USB disconnect, device number 5
[   76.712896] usb 1-1.2: new full-speed USB device number 6 using dwc_otg
[   76.824610] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=2763
[   76.824647] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1
[   76.824664] usb 1-1.2: Product: Raspberry Pi
[   76.824677] usb 1-1.2: Manufacturer: Broadcom
[   76.824691] usb 1-1.2: SerialNumber: Broadcom
[   79.029287] usb 1-1.2: USB disconnect, device number 6
[   79.772602] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
[   91.611592] usb 1-1.2: device not accepting address 7, error -110
[ 8051.127583] usb 1-1.2: new high-speed USB device number 9 using dwc_otg
[ 8057.827081] usb 1-1.2: device descriptor read/all, error -110
[ 8057.907099] usb 1-1.2: new high-speed USB device number 10 using dwc_otg
[ 8063.196711] usb 1-1.2: device descriptor read/all, error -110
[ 8068.536334] usb 1-1.2: new full-speed USB device number 12 using dwc_otg
[ 8068.646206] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=2763
[ 8068.646240] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 8068.646257] usb 1-1.2: Product: BCM2708 Boot
[ 8068.646271] usb 1-1.2: Manufacturer: Broadcom
[ 8070.089604] usb 1-1.2: USB disconnect, device number 12
[ 8070.326233] usb 1-1.2: new full-speed USB device number 13 using dwc_otg
[ 8070.437813] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=2763
[ 8070.437849] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1
[ 8070.437866] usb 1-1.2: Product: Raspberry Pi
[ 8070.437880] usb 1-1.2: Manufacturer: Broadcom
[ 8070.437893] usb 1-1.2: SerialNumber: Broadcom
[ 8072.393576] usb 1-1.2: USB disconnect, device number 13
[ 8073.396026] usb 1-1.2: new high-speed USB device number 14 using dwc_otg
[ 8079.585520] usb 1-1.2: device descriptor read/all, error -110
[ 8079.665561] usb 1-1.2: new high-speed USB device number 15 using dwc_otg
[ 8084.995115] usb 1-1.2: device descriptor read/all, error -110
[ 8085.075144] usb 1-1.2: new high-speed USB device number 16 using dwc_otg
[ 8095.494252] usb 1-1.2: device not accepting address 16, error -110
[ 9782.712038] usb 1-1.2: new high-speed USB device number 18 using dwc_otg
[ 9787.881627] usb 1-1.2: device descriptor read/all, error -110
[ 9787.961664] usb 1-1.2: new high-speed USB device number 19 using dwc_otg
[ 9793.291221] usb 1-1.2: device descriptor read/all, error -110
[ 9798.330925] usb 1-1.2: new full-speed USB device number 21 using dwc_otg
[ 9798.440802] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=2763
[ 9798.440838] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 9798.440857] usb 1-1.2: Product: BCM2708 Boot
[ 9798.440872] usb 1-1.2: Manufacturer: Broadcom
[ 9800.653988] usb 1-1.2: USB disconnect, device number 21
[ 9800.890747] usb 1-1.2: new full-speed USB device number 22 using dwc_otg
[ 9801.002337] usb 1-1.2: New USB device found, idVendor=0a5c, idProduct=2763
[ 9801.002407] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1
[ 9801.002428] usb 1-1.2: Product: Raspberry Pi
[ 9801.002443] usb 1-1.2: Manufacturer: Broadcom
[ 9801.002457] usb 1-1.2: SerialNumber: Broadcom
[ 9802.957990] usb 1-1.2: USB disconnect, device number 22
[ 9803.960473] usb 1-1.2: new high-speed USB device number 23 using dwc_otg
[ 9809.440089] usb 1-1.2: device descriptor read/all, error -110
[ 9809.520118] usb 1-1.2: new high-speed USB device number 24 using dwc_otg
[ 9820.039220] usb 1-1.2: device not accepting address 24, error -110
[ 9820.119336] usb 1-1.2: new high-speed USB device number 25 using dwc_otg
[ 9830.538428] usb 1-1.2: device not accepting address 25, error -110
[ 9830.618584] usb 1-1.2: new high-speed USB device number 26 using dwc_otg
[ 9835.638202] usb 1-1.2: device descriptor read/8, error -110
[ 9840.767769] usb 1-1.2: device descriptor read/8, error -110
[ 9840.877891] hub 1-1:1.0: unable to enumerate USB device on port 2

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Sat Jul 26, 2014 9:39 pm

Code: Select all

usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
This corresponds to the "Found serial = 0: writing file usbbootcode.bin"

Code: Select all

usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1
This corresponds to the "Found serial = 1: writing file msd.bin"

Code: Select all

usb 1-1.2: device descriptor read/all, error -110
This isn't good, for some reason you're getting USB errors. :(


For comparison, the corresponding section from my dmesg output looks like

Code: Select all

[ 7499.405434] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
[ 7499.515310] usb 1-1.5: New USB device found, idVendor=0a5c, idProduct=2763
[ 7499.515347] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7499.515365] usb 1-1.5: Product: BCM2708 Boot
[ 7499.515381] usb 1-1.5: Manufacturer: Broadcom
[ 7500.706226] usb 1-1.5: USB disconnect, device number 7
[ 7500.945742] usb 1-1.5: new full-speed USB device number 8 using dwc_otg
[ 7501.057392] usb 1-1.5: New USB device found, idVendor=0a5c, idProduct=2763
[ 7501.057430] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=1
[ 7501.057448] usb 1-1.5: Product: Raspberry Pi
[ 7501.057463] usb 1-1.5: Manufacturer: Broadcom
[ 7501.057480] usb 1-1.5: SerialNumber: Broadcom
[ 7503.010461] usb 1-1.5: USB disconnect, device number 8
[ 7504.016131] usb 1-1.5: new high-speed USB device number 9 using dwc_otg
[ 7504.117360] usb 1-1.5: New USB device found, idVendor=0a5c, idProduct=0001
[ 7504.117396] usb 1-1.5: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ 7504.117414] usb 1-1.5: Product: Compute Module
[ 7504.117429] usb 1-1.5: Manufacturer: Raspberry Pi
[ 7504.117445] usb 1-1.5: SerialNumber: 0001
[ 7504.121245] usb-storage 1-1.5:1.0: USB Mass Storage device detected
[ 7504.122029] scsi0 : usb-storage 1-1.5:1.0
[ 7505.117452] scsi 0:0:0:0: Direct-Access     Raspberr y PiMass storage      PQ: 0 ANSI: 2
[ 7505.122150] sd 0:0:0:0: [sda] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)
[ 7505.122629] sd 0:0:0:0: [sda] Write Protect is off
[ 7505.122661] sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00
[ 7505.123133] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 7505.130736]  sda: sda1 sda2
[ 7505.133842] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 7505.189018] sd 0:0:0:0: Attached scsi generic sg0 type 0
Have you got a separate (quality) power supply for each of your Raspberry Pi and Compute Module?
Are you using a USB hub or anything? (although in theory that shouldn't make any difference)

ShiftPlusOne
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4690
Joined: Fri Jul 29, 2011 5:36 pm
Location: The unfashionable end of the western spiral arm of the Galaxy

Re: Compute module not talking

Sat Jul 26, 2014 9:42 pm

I've had similar problems with other devices when there wasn't enough power to go around, so that's definitely worth checking.

Note that once rpiboot has done its thing, you can plug the compute module into any other computer to continue, as long as you don't unplug the power.

svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Re: Compute module not talking

Mon Jul 28, 2014 7:12 am

Have you got a separate (quality) power supply for each of your Raspberry Pi and Compute Module?
Are you using a USB hub or anything? (although in theory that shouldn't make any difference)
Tried another power supply, no difference.

I have had a small success using a different Windows machine booted into ubuntu 10 - I can see the Raspberr y mass stoage device, format the master boot record, partition it, copy files to it. Move it to another machine and the folder appears blank. Look at it from the Pi using lsblk and no device is listed. There seems to be read errors preventing it from being recognised. Sometimes the Windows format tool can see the FAT partition size, sometimes it is not recognised. SD formatter complains 'this drive is not supported' or 'cannot get device geometry.

I am convinced it is a hardware fault on the Compute/IO module.

svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Re: Compute module not talking

Tue Jul 29, 2014 3:22 pm

This does appear to be a hardware fault so Farnell are sending a replacement item.

Thanks for all the help in diagnosing this.

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Tue Jul 29, 2014 4:05 pm

Let us know if the replacement works any better :)

svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Re: Compute module not talking

Wed Jul 30, 2014 10:59 am

Let us know if the replacement works any better
The replacement works exactly as per the documentation. Boring.

That is (of course) RISC OS cannot see the EMMC memory yet. I have tried commenting out the 'init_emmc_clock=1000000' line in config.txt but still no joy. The Pico image works (can't see the SD card but it doesn't try to during start up), and CTRL-BREAK works (with the Pico image). However the RC12a image fails on restart (if you type CTRL-SHIFT-f12 then 'restsrt' the screen just stays blank).

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Wed Jul 30, 2014 11:19 am

svrsig wrote:
Let us know if the replacement works any better
The replacement works exactly as per the documentation. Boring.
Yay, that's good news then :D
That is (of course) RISC OS cannot see the EMMC memory yet. I have tried commenting out the 'init_emmc_clock=1000000' line in config.txt but still no joy. The Pico image works (can't see the SD card but it doesn't try to during start up), and CTRL-BREAK works (with the Pico image). However the RC12a image fails on restart (if you type CTRL-SHIFT-f12 then 'restsrt' the screen just stays blank).
Well, that's obviously up to the RISC OS developers to fix - if they think enough people will want to run RISC OS on the Compute Module for them to spend the effort 'fixing' it ;)

svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Re: Compute module not talking

Thu Jul 31, 2014 8:11 am

Well, that's obviously up to the RISC OS developers to fix - if they think enough people will want to run RISC OS on the Compute Module for them to spend the effort 'fixing' it
It is (at least) possible that RISC OS has some attraction for embedded devices. The changes to the source code to talk to the EMMC (rather than to an SD card) are likely to be trivial - any clues from the Linux community please?

I think the relevant source is here:
https://www.riscosopen.org/viewer/view/ ... er?rev=1.3

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 12:31 pm

Same here...received 2 compute boards from Farnell today...both show:

Code: Select all

Aug 15 14:28:03 nuc kernel: [713323.884376] usb 2-2: new full-speed USB device number 24 using xhci_hcd
Aug 15 14:28:08 nuc kernel: [713328.882477] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
Aug 15 14:28:13 nuc kernel: [713334.084631] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
Aug 15 14:28:13 nuc kernel: [713334.288508] usb 2-2: device not accepting address 24, error -62
Aug 15 14:28:18 nuc kernel: [713339.286717] xhci_hcd 0000:00:14.0: Timeout while waiting for a slot
Aug 15 14:28:18 nuc kernel: [713339.286731] hub 2-0:1.0: couldn't allocate port 2 usb_device
Seems to be a general bad hardware build...

Or if they would preload the flash they would see that some boards just don't work...

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 1:25 pm

Your error messages are slightly different to the ones that svrsig was getting... :?
Also, I think the xhci messages mean that you've plugged it into a USB3 port? Guess it wouldn't hurt to try using a USB2 port instead? *shrug*

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 1:33 pm

That's the only thing I have..besides Vmware on top of iMac with USB2.0 ports...and that doesn't work either (o;

It also shows:

Code: Select all

Aug 15 14:10:58 nuc kernel: [712299.214671] usb 2-1: device descriptor read/8, error -110
Aug 15 14:11:03 nuc kernel: [712304.332914] usb 2-1: device descriptor read/8, error -110
If it's a generell problem with USB3 ports, then this should be mentioned somewhere in a Wiki or the installation guide...

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 1:56 pm

Well...also directly under OSX it won't enumerate with USB2 ports:

Code: Select all

USBF:    322421.165    The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0xfa130000)
USBF:    322427.166    AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfa, timing out! (Addr: 0, EP: 0)
USBF:    322433.168    AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfa, timing out! (Addr: 0, EP: 0)
USBF:    322439.171    AppleUSBEHCI::Found a transaction which hasn't moved in 5000 milliseconds on bus 0xfa, timing out! (Addr: 0, EP: 0)
So no way libusb can use it....

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 2:34 pm

Hmmm, just done some tests myself, and I also can't get rpiboot talking to the Compute Module over a USB3 port. But I'm still running Ubuntu 12.04 (kernel 3.2.0) so I dunno if that's just because of my old kernel using out-of-date USB3 drivers :?
It (rpiboot) also doesn't work if I plug the CM into a USB2 hub into a USB3 port.

However rpiboot and CM work just fine in a USB2 port, or in a USB2 hub connected to a USB2 port. And as http://www.raspberrypi.org/documentatio ... lashing.md mentions, you can also run rpiboot on a RaspberryPi :) (which obviously doesn't have USB3 ports!)

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 2:48 pm

That would have been my next try...using a RPi B+ for that (o;

Also tried with a USB2 hub before..same....

Even powered with a proper power supply..namely HP 6632B, a little overkill maybe (o;
But then whole system froze with the compute module and GPIB plugged in...

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 3:38 pm

That worked with a RPi as host...

Code: Select all

root@raspberrypi:/home/pi/tools/usbboot# ./rpiboot
Waiting for BCM2835 ...
Found serial = 0: writing file usbbootcode.bin
Successful
Waiting for BCM2835 ...
Found serial = 1: writing file msd.bin
Successful
Raspberry Pi is now a mass storage device, use lsblk to find it
root@raspberrypi:/home/pi/tools/usbboot# lsblk
NAME        MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0     179:0    0  59G  0 disk 
├─mmcblk0p1 179:1    0  56M  0 part /boot
└─mmcblk0p2 179:2    0  59G  0 part /
Just lsblk" won't show it.....but unplugging the compute module and replug to the Ubuntu PC shows it now as /dev/sdb entry where I can dd the raspbian image to it...

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 4:00 pm

Good to know that your boards aren't in fact faulty then :D

After posting my last comment I tried rpiboot on my B+ Pi, and it and lsblk both worked just fine... :?

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 4:07 pm

Hmm...takes ages to dd to the USB device...still ongoing...

Saw in the dmesg log that it actually assigned /dev/sg0...maybe I was too quick issuing "lsblk"...
Well...there is another board waiting to try out....

Meanwhile compiling rtl-sdr for my dvb-t sticks ;-)

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 4:10 pm

davorin wrote:Hmm...takes ages to dd to the USB device...still ongoing...
Apparently eMMC is optimised for small random reads/writes (that an OS would typically do), so perhaps it's slower than SD cards for big contiguous reads/writes (that a digital camera and 'dd' would typically do) :?: *shrug*

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 6:26 pm

Stopped it now after 2 hours....trying now to "dd" from the Raspberry Pi itself...

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Fri Aug 15, 2014 8:03 pm

Hmm...can't be installing onto eMMC takes more than 2 hours???

I seriously doubt the hardware design of this RPi dev kit.....


Shitloads of log messages:

Code: Select all

[14696.485359] usb 1-1.2: reset high-speed USB device number 8 using dwc_otg
[14727.485823] usb 1-1.2: reset high-speed USB device number 8 using dwc_otg
[14758.486265] usb 1-1.2: reset high-speed USB device number 8 using dwc_otg
[14789.486728] usb 1-1.2: reset high-speed USB device number 8 using dwc_otg
[14820.487177] usb 1-1.2: reset high-speed USB device number 8 using dwc_otg
[14851.487620] usb 1-1.2: reset high-speed USB device number 8 using dwc_otg
[14851.588579] sd 0:0:0:0: [sda] Unhandled error code
[14851.588617] sd 0:0:0:0: [sda]  
[14851.588631] Result: hostbyte=0x05 driverbyte=0x00
[14851.588645] sd 0:0:0:0: [sda] CDB: 
[14851.588654] cdb[0]=0x2a: 2a 00 00 00 46 50 00 00 f0 00
[14851.588695] end_request: I/O error, dev sda, sector 18000
[14851.588713] quiet_error: 20 callbacks suppressed
[14851.588728] Buffer I/O error on device sda, logical block 2250
[14851.588737] lost page write due to I/O error on sda
[14851.588774] Buffer I/O error on device sda, logical block 2251
[14851.588785] lost page write due to I/O error on sda
[14851.588803] Buffer I/O error on device sda, logical block 2252
[14851.588813] lost page write due to I/O error on sda
[14851.588829] Buffer I/O error on device sda, logical block 2253
[14851.588840] lost page write due to I/O error on sda
[14851.588856] Buffer I/O error on device sda, logical block 2254
[14851.588866] lost page write due to I/O error on sda
[14851.588881] Buffer I/O error on device sda, logical block 2255
[14851.588891] lost page write due to I/O error on sda
[14851.588906] Buffer I/O error on device sda, logical block 2256

svrsig
Posts: 134
Joined: Thu Nov 03, 2011 9:45 am
Contact: Website

Re: Compute module not talking

Sat Aug 16, 2014 8:29 am

When it does work (and the replacement board works perfectly), the transfer speed to the CM as a mass storage device should be about 7Mbytes/sec. Hence 10 minutes to flash 4Gbytes. Two hours is (IMHO) a hardware fault.

With the faulty CM board in its IO module, I found that lsblk on a Pi would consistently not see the mass storage device but Ubunto10 on a desktop machine would see it but (sometimes, and on other machines very quickly) threw write errors after a few files had been copied. It also seemed that I could only get that far if I used a 5V 2A power supply for the CM/IO board rather than a 1A supply.

The faulty board was replaced by Farnell by return of post and a reply-paid label brought to my front door a few days later to RMA the faulty device. Very good service!

davorin
Posts: 167
Joined: Tue Sep 11, 2012 2:07 pm
Location: Switzerland
Contact: Website

Re: Compute module not talking

Sat Aug 16, 2014 9:04 am

Strange that both boards show this hardware fault...

Now even crashes when using an RPi as host:

Code: Select all

Aug 16 09:03:06 raspberrypi kernel: [  369.276701] usb 1-1.5: reset high-speed USB device number 6 using dwc_otg
Aug 16 09:03:37 raspberrypi kernel: [  400.277202] usb 1-1.5: reset high-speed USB device number 6 using dwc_otg
Aug 16 09:04:08 raspberrypi kernel: [  431.277637] usb 1-1.5: reset high-speed USB device number 6 using dwc_otg
Aug 16 09:04:39 raspberrypi kernel: [  462.278116] usb 1-1.5: reset high-speed USB device number 6 using dwc_otg
Aug 16 09:04:58 raspberrypi kernel: [  481.228476] kworker/u2:2    D c0421bec     0    38      2 0x00000000
Aug 16 09:04:58 raspberrypi kernel: [  481.228573] Workqueue: writeback bdi_writeback_workfn (flush-8:0)
Aug 16 09:04:58 raspberrypi kernel: [  481.228675] [<c0421bec>] (__schedule+0x288/0x568) from [<c0422478>] (io_schedule+0x88/0xe4)
Aug 16 09:04:58 raspberrypi kernel: [  481.228762] [<c0422478>] (io_schedule+0x88/0xe4) from [<c0220b28>] (get_request+0x16c/0x644)
Aug 16 09:04:58 raspberrypi kernel: [  481.228838] [<c0220b28>] (get_request+0x16c/0x644) from [<c0221ecc>] (blk_queue_bio+0x64/0x2d8)
Aug 16 09:04:58 raspberrypi kernel: [  481.228907] [<c0221ecc>] (blk_queue_bio+0x64/0x2d8) from [<c0220190>] (generic_make_request+0xac/0xcc)
I don't see a diffference between 1A and 2A supply...currently powering with an Agilent 6632B and it tells me via GPIB:

Code: Select all

ibterm>MEAS:CURR?
5.66764E-2
ibterm>
So only 57mA consumption...with a peak at 80mA when starting writing...

HAven't got a reply so far from Farnell....but I'm sure they will replace it...far better RMA service than Mouser, where you have to fill out the Fedex/UPS forms all by yourself (o;

Return to “Compute Module”

Who is online

Users browsing this forum: No registered users and 3 guests