Solved 12864 stopped working in 3.4b6
-
@jltx Yeah. Not meant to critizise, more a personal reflection.
Regarding webcams, there are quite a few standalone cams, esp32-based with wifi and builtin webserver that I imagine could be quite handy .
I wonder though if not gloomyandy was onto something there with the firmware on the Duet and the menu files on the Pi. I guess you have checked that the menu files and all that is present in the Pi filesystem? I know nothing about the SBC so I couldn't tell you how it's supposed to be placed
-
i'm pretty sure my fysetc mini display is working on my mini 5+ running 3.4b6. i'll check tonight
-
-
@jltx said in 12864 stopped working in 3.4b6:
So if I put 3.4 into duet that will work? I thought that was some different tethered version of firmware.
Yeah, that doesn’t run at all. I’ll have to create a third SD with standalone 3.4.
-
@jltx I think you may be getting confused as to what happens when you put an SD card into your Duet board (apologies if you already know this)...
If you are using a Duet board there is no such thing as a standalone or SBC version of the firmware. The same firmware will run in standalone mode if there is an SD card in the drive on the duet board and in SBC mode if there is not an SD card in the duet boards drive. So if your board has v3.4b6 installed then that is the version that will be running in both standalone and in SBC mode irrespective of the SD card. You can confirm this by running the M122 command which will show you the version of the firmware.
The contents of the SD card do not change the version of the firmware being run (you need to take extra steps to change the version of the firmware that is actually installed on the board). So simply swapping the SD card will not change the executing firmware from say 3.3.0 to 3.4b6, it may change the configuration files being used, but not the version of the firmware.
To confuse things further, the SD card that comes with the duet contains two different filesystems, one that is normally read by Windows type machines and by the Duet board directly. The other is a Linux filesystem that will only be read by the rPi when being used as a SBC. Because of this you may have two different sets of configuration files on the same SD card (one that will be used when the card is placed in the card reader of the Duet and one that will be used when the same card is being used in the rPi).
The second point above raises the question of how did you put the menu files onto the SBC version of your setup. Did you upload the files using DWC when the board was running in SBC mode (or use some other sort of Linux program to install them)? If not it is possible that the menu files are not on the Linux part of the SD card and are therefore not being used by your display.
-
@gloomyandy yes, I am massively confused. When I looked at the object model it showed 3.3 with my old card. So I never succeeded in upgrading to 3.4? The weird part is that 3.4 had a change I needed which did resolve that problem. Hmm. I would check this out but now my duet has stopped connecting to my wifi in any of the configurations and I have no way to fix that without tearing down my printer.
I did install the menu files through DWC. But I think I need to start over. I followed all the steps in https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation to get the unstable build installed. Now I'm questioning my sanity.
-
@gloomyandy
OK, it was just my router messing with me. So I booted in standalone using my "3.3" SD and it does indeed show that the firmware is actually 3.4b6. So what are the bin files in the firmware directory for? When I was missing those it would not boot and once I added them it booted correctly. But those bin are from 3.3 since that card was not used in the upgrade.So anyway, clearly the 12864 works with 3.4 and so the failure mode must be SBC. Sorry for my embarrassing ignorance. Which forum category covers SBC?
-
@jltx The bin files you can see in the firmware directory of the SD card are used when in standalone mode to updated the firmware. But they will only be used when you issue the M997 command (or something like DWC does it for you).When you do this a combination of the current firmware and bootloader will copy the new firmware from the SD card and place it into the flash memory of the mcu. Once this operation is complete the mcu will simply run this code from the built in flash memory when it boots, it will not re-read the firmware files from the SD card. When you are running in SBC mode the firmware files are stored on the SD card in the SBC (as part of the Linux filesystem I described above) and are sent to the duet board when you issue the M997 command, again to be stored in the built in flash memory.
-
@gloomyandy I found one problem. When I upgraded from 3.3 to 3.4 it erased all of my directories and replaced them with empty and I lost all of my careful printer configuration. I lost days of work so I'm going to take a break from duet for a while.
-
@jltx said in 12864 stopped working in 3.4b6:
@gloomyandy I found one problem. When I upgraded from 3.3 to 3.4 it erased all of my directories and replaced them with empty and I lost all of my careful printer configuration. I lost days of work so I'm going to take a break from duet for a while.
How did you upgrade? Did you check the SD card in a PC?
-
@phaedrux I cut and paste each step from the wiki into ssh on pi. when I pulled the SD and looked at the contents I see all empty directories with just a template config.g in sys.
I have reconstructed much of it now. Is there a simple way to generate a backup through DWC? getting at the SD is a real pain in my installation. I don't want to lose it again.
-
@jltx said in 12864 stopped working in 3.4b6:
I’m using an external power supply for the rpi. Do I have a ground plane mismatch? Can I power from the duet 5v over the ribbon?
Solved! I put in the jumpers suggested by @Gixxerfast and it works perfectly again. Not sure if it was the ground plane but I'm going to take full credit for that. <pats self on back>
-
@jltx said in 12864 stopped working in 3.4b6:
I cut and paste each step from the wiki into ssh on pi. when I pulled the SD and looked at the contents I see all empty directories with just a template config.g in sys.
If you're using a raspberry pi, the SD card is not a readable format in a windows computer. The config files are located in the linux file system on the pi.
-
undefined dc42 marked this topic as a question
-
undefined dc42 has marked this topic as solved
