Most recent activity
-
I have now tried the device on 2 Linux machines, a Windows 7 and a Windows 8 machines, I get the same symptoms everywhere.
I guess that means that one of my boards has a hardware problem, or is there any other explanation? -
i also get 2628236757068185765 so that seems fine
-
As suggested here: http://www.espruino.com/Quick+Start for linux run:
sudo adduser _YOUR_USERNAME_HERE dialoutand then try again (if that doesn't already solve it, which for me it didn't) do this:
sudo chmod ugo+rw /dev/ttyACM0
and then try again, note that if that solves it for you, you'll have to run this everytime you reconnect the board (so it should only be used as a temporary solution)
-
I tried your suggestions (holding the reset button longer or plugging i in with btn1 pressed). However I always see the same behaviour (blue and red light lighting up).
I also tried again with the other (working) board, there it always works and the bootloader is able to connect withing a fraction of a second (led changes to pulsating blue).
Changing back to the windows machine and trying the same things didn't show any difference.
The problem-device currently has V1.43 the other one that i managed to update V1.47 and i just upgraded it to V1.48.
Are there any other things i can try to update my second board (and yes you assumed correctly that the "normal" mode is working fine on the board, both on linux and windows.
In Windows, when trying to connect the device in bootloader mode, this window pops up: http://prntscr.com/2o1get
-
Hy, I received my 2 Espruinos yesterday. After firing on of them up, I realized that it still had a slightly old firmware on it with that regression bug where some characters after each function have to be inserted to make it work.
Now i tried to upgrade the 2 espruinos (via the chrome IDE as explained in the guide), it worked like a charm for the first device.
When i tried to do it with the second one, i realized that the bootloader LED wasn't pulsating as described (and as my first device did). Instead the blue & red (LED1&3) are both lighting up very bright and staying that way until i press the reset button again. I first thought this had sth to do with my windows laptop. The device also isn't recognized as a serial device anymore when it is in this state.Now i tried it on my linux laptop with the same result. Here is the syslog output i get (first doing a normal reset and then the btn+reset reset for the bootloader)
# reset espruino normally Jan 30 19:48:18 paulbook3 kernel: [ 1028.760404] usb 2-1.2: new full-speed USB device number 37 using ehci-pci Jan 30 19:48:18 paulbook3 kernel: [ 1028.855671] usb 2-1.2: New USB device found, idVendor=0483, idProduct=5740 Jan 30 19:48:18 paulbook3 kernel: [ 1028.855687] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 30 19:48:18 paulbook3 kernel: [ 1028.855696] usb 2-1.2: Product: STM32 Virtual COM Port Jan 30 19:48:18 paulbook3 kernel: [ 1028.855704] usb 2-1.2: Manufacturer: STMicroelectronics Jan 30 19:48:18 paulbook3 kernel: [ 1028.855712] usb 2-1.2: SerialNumber: 48E074533330 Jan 30 19:48:18 paulbook3 kernel: [ 1028.857526] cdc_acm 2-1.2:1.0: This device cannot do calls on its own. It is not a modem. Jan 30 19:48:18 paulbook3 kernel: [ 1028.857635] cdc_acm 2-1.2:1.0: ttyACM0: USB ACM device Jan 30 19:48:18 paulbook3 mtp-probe: checking bus 2, device 37: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2" Jan 30 19:48:18 paulbook3 mtp-probe: bus: 2, device: 37 was not an MTP device # try to put device into bootloader mode Jan 30 19:48:22 paulbook3 kernel: [ 1033.426277] usb 2-1.2: USB disconnect, device number 37 Jan 30 19:48:23 paulbook3 kernel: [ 1033.626612] usb 2-1.2: new full-speed USB device number 38 using ehci-pci Jan 30 19:48:23 paulbook3 kernel: [ 1033.698622] usb 2-1.2: device descriptor read/64, error -32 Jan 30 19:48:23 paulbook3 kernel: [ 1033.874694] usb 2-1.2: device descriptor read/64, error -32 Jan 30 19:48:23 paulbook3 kernel: [ 1034.050810] usb 2-1.2: new full-speed USB device number 39 using ehci-pci Jan 30 19:48:23 paulbook3 kernel: [ 1034.122837] usb 2-1.2: device descriptor read/64, error -32 Jan 30 19:48:23 paulbook3 kernel: [ 1034.298915] usb 2-1.2: device descriptor read/64, error -32 Jan 30 19:48:24 paulbook3 kernel: [ 1034.474971] usb 2-1.2: new full-speed USB device number 40 using ehci-pci Jan 30 19:48:24 paulbook3 whoopsie[1076]: online Jan 30 19:48:24 paulbook3 kernel: [ 1034.883016] usb 2-1.2: device not accepting address 40, error -32 Jan 30 19:48:24 paulbook3 kernel: [ 1034.955220] usb 2-1.2: new full-speed USB device number 41 using ehci-pci Jan 30 19:48:24 paulbook3 kernel: [ 1035.363240] usb 2-1.2: device not accepting address 41, error -32 Jan 30 19:48:24 paulbook3 kernel: [ 1035.363408] hub 2-1:1.0: unable to enumerate USB device on port 2 Jan 30 19:48:25 paulbook3 whoopsie[1076]: onlineIs this a known problem? How can I update that second device?
Holy cow... :D
I just flashed the device that was making problems. I found a way to put it into bootloader mode (get the pulsating blue led). The trick is: pressing the BTN1 button hard.
This is totally reproducable on my board, if i press BTN1 normally (i hear the click sound and it obviously does something because after releasing RST the red & blue LEDs light up).
But I press BTN1 hard (to a point where i see the PCB slightly bending already - just barely visible, not total brute-force) and then press & release RST it goes into the bootloader mode just fine (red & blue LEDs go away after fraction of a second and i get to pulsating blue LED).
Sooo... i don't really know what that means (maybe one of the BTN1 solder-connections isn't 100% ok?) but anyhow: i have now updated my second board :) that's a relief.
Thanks for your help!