No Connection to DCS After Update to 3.2beta4
-
[ 3.113716] mmc0: new high speed SDHC card at address aaaa
[ 3.122622] mmcblk0: mmc0:aaaa SC16G 14.8 GiB
[ 3.138886] mmcblk0: p1 p2
[ 3.149149] mmc1: new high speed SDIO card at address 0001
[ 3.188390] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[ 3.196235] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[ 3.227091] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 3.235175] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.244043] hub 1-1:1.0: USB hub found
[ 3.252171] hub 1-1:1.0: 4 ports detected
[ 3.576710] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 3.707374] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[ 3.715455] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.725844] hub 1-1.1:1.0: USB hub found
[ 3.734122] hub 1-1.1:1.0: 3 ports detected
[ 3.836756] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[ 4.099654] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
[ 4.108359] EXT4-fs (mmcblk0p2): 3 orphan inodes deleted
[ 4.116202] EXT4-fs (mmcblk0p2): recovery complete
[ 4.146925] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.155017] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 4.167076] devtmpfs: mounted
[ 4.182104] Freeing unused kernel memory: 1024K
[ 4.190411] Run /sbin/init as init process
[ 4.376741] usb 1-1.2: device not accepting address 4, error -71
[ 4.476752] usb 1-1.1.2: new low-speed USB device number 5 using dwc_otg
[ 4.611133] usb 1-1.1.2: New USB device found, idVendor=17ef, idProduct=6019, bcdDevice= 1.00
[ 4.619252] usb 1-1.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 4.627155] usb 1-1.1.2: Product: Lenovo Optical USB Mouse
[ 4.646553] input: Lenovo Optical USB Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0/0003:17EF:6019.0001/input/input0
[ 4.655718] hid-generic 0003:17EF:6019.0001: input,hidraw0: USB HID v1.11 Mouse [Lenovo Optical USB Mouse] on usb-3f980000.usb-1.1.2/input0
[ 4.706730] usb 1-1.2: new high-speed USB device number 6 using dwc_otg
[ 4.831182] systemd[1]: System time before build time, advancing clock.
[ 4.982563] NET: Registered protocol family 10
[ 4.992662] Segment Routing with IPv6
[ 5.040050] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 5.073497] systemd[1]: Detected architecture arm.
[ 5.186972] systemd[1]: Set hostname to <VCorePro>.
[ 6.172245] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.199427] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.209447] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 6.231478] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.241753] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 6.263083] systemd[1]: Reached target Swap.
[ 6.285392] systemd[1]: Listening on Journal Socket.
[ 6.307904] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 6.318731] systemd[1]: Listening on Syslog Socket.
[ 6.341599] systemd[1]: Listening on udev Control Socket.
[ 6.535966] i2c /dev entries driver
[ 7.426144] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 7.577462] systemd-journald[112]: Received request to flush runtime journal from PID 1
[ 8.314626] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.319998] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 8.320071] [vc_sm_connected_init]: start
[ 8.327723] [vc_sm_connected_init]: installed successfully
[ 8.332761] mc: Linux media interface: v0.10
[ 8.425609] videodev: Linux video capture interface: v2.00
[ 8.466083] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.467342] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.469227] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.481384] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.483268] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.489272] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 8.500514] bcm2835_audio bcm2835_audio: card created with 4 channels
[ 8.513179] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
[ 8.514526] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
[ 8.515435] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
[ 8.515981] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
[ 8.516012] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
[ 8.516034] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
[ 8.516053] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
[ 8.516071] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
[ 8.516411] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[ 8.522960] bcm2835_audio bcm2835_audio: card created with 4 channels
[ 8.526911] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 8.526971] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 8.811375] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 8.959695] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 9.059962] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 9.074493] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 9.075716] usbcore: registered new interface driver brcmfmac
[ 9.112549] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
[ 9.165886] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 9.165946] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 9.185081] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 9.185139] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 9.198687] bcm2835-v4l2: scene mode selected 0, was 0
[ 9.199547] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 1280x720
[ 9.205789] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.
[ 9.206442] random: crng init done
[ 9.206457] random: 7 urandom warning(s) missed due to ratelimiting
[ 9.396794] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 9.447122] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea
[ 9.856751] usb 1-1.2: device descriptor read/64, error -110
[ 11.327971] 8021q: 802.1Q VLAN Support v1.8
[ 11.664692] uart-pl011 3f201000.serial: no DMA platform data
[ 11.920530] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 12.007895] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 17.730065] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 18.543579] Bluetooth: Core ver 2.22
[ 18.543819] NET: Registered protocol family 31
[ 18.543827] Bluetooth: HCI device and connection manager initialized
[ 18.543921] Bluetooth: HCI socket layer initialized
[ 18.543936] Bluetooth: L2CAP socket layer initialized
[ 18.543969] Bluetooth: SCO socket layer initialized
[ 18.563964] Bluetooth: HCI UART driver ver 2.3
[ 18.563979] Bluetooth: HCI UART protocol H4 registered
[ 18.564033] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 18.564212] Bluetooth: HCI UART protocol Broadcom registered
[ 19.132246] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.132266] Bluetooth: BNEP filters: protocol multicast
[ 19.132305] Bluetooth: BNEP socket layer initialized
[ 19.203665] Bluetooth: RFCOMM TTY layer initialized
[ 19.203712] Bluetooth: RFCOMM socket layer initialized
[ 19.203746] Bluetooth: RFCOMM ver 1.11
[ 19.444977] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use net.ipv6.neigh.wlan0.retrans_time_ms instead
[ 19.606888] fuse: init (API version 7.31)
[ 25.217241] usb 1-1.2: device descriptor read/64, error -110
[ 25.337424] usb 1-1-port2: attempt power cycle
[ 25.936739] usb 1-1.1.3: new low-speed USB device number 7 using dwc_otg
[ 26.103444] usb 1-1.1.3: New USB device found, idVendor=03f0, idProduct=2b4a, bcdDevice= 2.48
[ 26.103479] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 26.103488] usb 1-1.1.3: Product: HP USB Slim Keyboard - Skylab EU
[ 26.103501] usb 1-1.1.3: Manufacturer: Lite-On Technology Corp
[ 26.121085] input: Lite-On Technology Corp HP USB Slim Keyboard - Skylab EU as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:03F0:2B4A.0002/input/input1
[ 26.187607] hid-generic 0003:03F0:2B4A.0002: input,hidraw1: USB HID v1.10 Keyboard [Lite-On Technology Corp HP USB Slim Keyboard - Skylab EU] on usb-3f980000.usb-1.1.3/input0
[ 26.208820] input: Lite-On Technology Corp HP USB Slim Keyboard - Skylab EU Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.1/0003:03F0:2B4A.0003/input/input2
[ 26.277370] input: Lite-On Technology Corp HP USB Slim Keyboard - Skylab EU System Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.1/0003:03F0:2B4A.0003/input/input3
[ 26.279702] input: Lite-On Technology Corp HP USB Slim Keyboard - Skylab EU as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.1/0003:03F0:2B4A.0003/input/input4
[ 26.284425] hid-generic 0003:03F0:2B4A.0003: input,hiddev96,hidraw2: USB HID v1.10 Device [Lite-On Technology Corp HP USB Slim Keyboard - Skylab EU] on usb-3f980000.usb-1.1.3/input1
[ 26.576745] usb 1-1.1.2: reset low-speed USB device number 5 using dwc_otg
[ 27.216964] usb 1-1.2: new high-speed USB device number 8 using dwc_otg
[ 27.656971] usb 1-1.2: device not accepting address 8, error -71
[ 27.756804] usb 1-1.2: new high-speed USB device number 10 using dwc_otg
[ 32.797137] WARN::dwc_otg_hcd_urb_dequeue:638: Timed out waiting for FSM NP transfer to complete on 3
[ 38.077139] WARN::dwc_otg_hcd_urb_dequeue:638: Timed out waiting for FSM NP transfer to complete on 6
[ 38.296761] usb 1-1.2: device not accepting address 10, error -110
[ 38.296928] usb 1-1-port2: unable to enumerate USB device
[ 38.396765] usb 1-1.1.1: new high-speed USB device number 9 using dwc_otg
[ 38.527342] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
[ 38.527360] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 38.791992] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
[ 38.792835] libphy: lan78xx-mdiobus: probed
[ 38.808968] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
[ 39.243110] 8021q: adding VLAN 0 to HW filter on device eth0
pi@ -
try reseting the board again.
-
@Veti how long do i have to press the reset button when i power it up ? in the meanwhile , i flashed a complete new image on a other (fresh) sd card with 8Gb. The same Problem. After the first start when the welcome window appears , the DWC Window is opening and imideatly i get the error message Failed to connect to duet3
-
normally not at all since you place a jumper across the ERASE pins on the Duet 3.
see
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware -
@Veti i did that too several times. when im verifying the image, bossa stops at ~line 1051. if i try to flash with the 3 options aktivatet, bossa crashes 1 second after the write window appears
-
can you try a different usb cable?
-
@Veti yes
-
@Veti the diag led is shining when i connect the board without sbc and vin over usb. ThE Light is not blinking. its static
-
yes if the firmware is erased, the diag led should be on constant
-
some people have had to use up to 18 different cable until they found one that worked.
-
@Veti you are joking, right ?!? 18 Cables....holy...i cant find what the meaning of the static diage led is ?
-
see
https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respondIf the firmware has been erased the DIAG LED will be on permanently.
-
@Veti Thank You SOooooooOO much for your tip with the usb cable....i tried a 10 year old usb2 dvd cable (with dual A Plugs on one side). After connecting the second the firmware flashed perfektly on the first try ;).
I would be so lost without you guys and this forum
Have a nice Day !
-
@Frederikfor information purposes:
The cable that did NOT work: brand new Ugreen with 3Meters in lenght.
The cable THAT worked: 10 Year old usb2.0 with dual USB-A Plug on one side.
Like the on the external dvd or harddrives. Lenght ~ 40cm -
So, the cable worked. The firmware flash over bossa worked. Also verifying. I did 2 times exact what's mentioned in the getti g startet wiki. I loaded the additional files, flashed a new copy of duet pi desktop on the 16gb card. After that I copied my .g files in the /sys folder on the boot partition together with the 3.1.1 firmware .bin.
After that, I Did all the steps like network, keyboard layout etc. Without any errors.
Even the update at the end + restart showed no errors. Only in the dcs log is constantly starting and stoping with the meassage:
No connection to duet3
Should I do a standalone firmware reset and after that reconnecting the pi?
It seems that the reset button did not reset the board, even if I hold it like 10 seconds
-
I do all the actual test without Vin.
Only connection over usb and wlan -
@Frederik said in No Connection to DCS After Update to 3.2beta4:
Should I do a standalone firmware reset and after that reconnecting the pi?
Yes I would set it up in standalone to confirm that the Duet is working correctly otherwise and see what firmware version is flashed.
-
@Phaedrux Thanks. I will test that later.
-
-
@chrishammyes, i have the unstable all the time.
After i changed to the standalone mode, made the specific sd card + filestrukture, the board accepted the firmware and the diag led is now out . after that i startet a complete new installation with the pi.
this time everything works fine..
The new Visualizer is amazing
Tomorrow i will install and test the new DuetLapse .But that way did not work at first with the sbc attached.
Thanks for all your help
Regards
Frederik
