Not reading config.g on startup.
-
So I have board number 2 now, and so far it appears I have the same issue. Refusing to believe I have two boards with this issue, I'm trying to re-flash the firmware, but so far no luck. After I re-flash it and press reset it won't connect. I'm going to try somemore tonight, but is it possible I have two boards now that won't read from the SD card? This is getting frustrating.
Dumb question I know but your not accidentally pressing "erase" as well or instead of "reset" are you? The buttons are very close together. In any case, I don't think you need to press reset after re-flashing the firmware.
No the erase button is placed back a little on this version of the board, so it would be difficult to press the erase button accidentally. I was following the wiki about pressing reset, but I'll try it tonight without pressing reset.
-
If you have re-flashed with 1.18.1 firmware and you were previously using an older version, and you are using a Windows usb host computer, did you install the new device driver as described in the upgrade notes?
-
If you have re-flashed with 1.18.1 firmware and you were previously using an older version, and you are using a Windows usb host computer, did you install the new device driver as described in the upgrade notes?
I think it previously already had 1.18.1 firmware, but I'm just trying anything at this point. I did install the device driver. I tried using the new Bossa on my Mac, and I've tried using the Sam-ba 2.16 on windows 10 virtual machine on my mac. On the windows machine I installed the device driver.
-
Ok. I've tried the 1.18.1 firmware and the new 1.19 beta, and either one will not connect after I refresh. I tried it without refreshing but it won't connect that way either. Any ideas? I'm afraid I'm going to have to return this board as well.
-
Are you able to connect via USB? If so, run M115 to confirm which firmware version you are running, because there have been big changes in the 1.19beta.
-
No I can't. The only way it lets me connect is if I erase and then reset. I can't get it to boot up with the firmware.
-
Have you checked the size of the Firmware download from github to make sure you have actually got the BIN File and not the webpage
-
Have you checked the size of the Firmware download from github to make sure you have actually got the BIN File and not the webpage
Yeah I checked that. I'll look again tonight, but I did look at that.
-
Does any sort of port, or an unknown device, show up in Device Manager (if you are using Windows) when you connect the Duet via USB after flashing the new firmware?
-
Also check that you re-named the files mind that wont matter if your loading the FW By Bossac or Samba
-
Also check that you re-named the files mind that wont matter if your loading the FW By Bossac or Samba
I've tried both Boassac and Samba. Neither one seems to work. I tried renaming the files before using Bossac and Samba, doesn't seem to matter.
-
Does any sort of port, or an unknown device, show up in Device Manager (if you are using Windows) when you connect the Duet via USB after flashing the new firmware?
No it doesn't. The windows is a VM on my mac that I can control where the USB ports connect and as soon as I reset the connection goes away and doesn't show up on the mac or the windows.
-
If it doesn't even show up as a COM port or unknown USB device, that suggests that the file you have flashed is not a valid firmware files for that board.
The DuetWiFiFirmware-1.18.1.bin file you downloaded should be 263Kb (268,852 bytes) long.
Also, please make sure that the M552 S1 command in config.g is commented out with a semicolon at the start of the line. WiFi firmware that doesn't match the main firmware can prevent the board running when the WiFi is enabled.
btw it's now possible to flash Duet WiFi firmware using the Bossa program from Shumatec, and there is a build of that program available for Mac.
-
So I was finally able to get the firmware reloaded. But now I'm getting as before where it says it cannot find the config file.
M503
SENDING:M503
Configuration file not found!
M21
SENDING:M21
Cannot initialise SD card 0: Card is unusable -
Have you tried a different SD card?
-
I've tried it with two different cards and with 1.18 firmware and 1.19 firmware. I still get the same Cannot initialize SD card error. Both SD cards are 8gb cards. One is the Kingston card that came with the board. The other is a card that came with my original Tronxy kit.
-
Is sounds like a faulty SD card socket then. Ask your supplier to replace the Duet.
-
Ok. Thanks. This is the second one in a row from that supplier. Any chance this is a whole batch?
-
That sounds most unlikely. The test procedure for Duets reads the test file from SD card, so the SD card socket is known to work when the board passes testing. Are you sure that both SD cards are OK - do they work in other equipment? How often are you removing and replacing the SD card in the Duet?
-
Any chance you're using an SD card extension cable?
How are you powering the Duet? If by USB, have you tried a different USB cable or powering it by the screw terminals?
As for concerns about it being a whole batch, I know you got it from us (Filastruder) and I don't believe we've had any other similar reports.
