MarlinFirmware
ABM doesn't set environment
I had to go to extension settings and put environment in default env variable, then in extension sidebar use the "build" button to use the default environment. If I click on "build" next to the environment in ABM, it just sets "<env>" and powerShell gets angry as shown below.
Same here, suddenly abm stopped working after months of use. Found out that the buttons in the ab left panel (green circle) does work as expected. Ab is only a helptool for platformio, directly build the package is not much more work if these buttons also stops obeying you.
I also have this issue, first time using platformio and ABM so this was quite annoying to deal with
Can imagine that, if you dont't know how software must behave and present you a meaningless error message than you need at least a few drinks. ;) If you know your board/mcu you can ignore the autobuilder and use platformio only, if you select the right environment in my case a SKR 1.4 turbo, you select LPC1769, (it is a long list and can be confusing) this is the processor/mcu used on this board. If selected you see 'build' to compile your software and 'clean', cleaning deletes the directory where the firmware is written to after the build, (don't forget to copy the compiled firmware first) it deletes the build to be ready for the next build. Usually you can find the firmware in the '.pio' folder, (in my case the marlin2.1.2.5 folder) this folder is in the root of your firmware directory (autobuild opens this folder automatically after the build) In this directory you find a lot of files after the build is done, you need only 'firmware.bin' if you flash marlin with a sd card, copy this to the root of a sd card wich must be fat32 preferable 8 gig or less, my board accept only a 4 gig card, depends on brand what work or not, another annoying issue where a drink is mandatory if not working. ;) To check if the firmware is succesfully is loaded... (sometimes not clear if you flash same firmware with different settings) check the sd card, if firmware.bin changed in to FIRMWARE.CUR than it was succefully done. Don't forget after the flash to erase the eeprom and store usually done in the display of your printer, or M501 for erase and M500 to store/safe if you can send these codes to your hardware with your pc. Happy compiling!!!
I'm new to this.... can someone explain easily how to get around this?
Did you see https://github.com/MarlinFirmware/AutoBuildMarlin/issues/96#issuecomment-3646692542? They say to use a different button and it works.
I'm new to this.... can someone explain easily how to get around this?
Read the post from the start, there is your answer. Than read my previous post with a workflow if you won't or can't use the autobuilder. Ask if there is something not clear!
"I had to go to extension settings and put environment in default env variable, then in extension sidebar use the "build" button to use the default environment." - where are these? And what is the environment i enter
"I had to go to extension settings and put environment in default env variable, then in extension sidebar use the "build" button to use the default environment." - where are these? And what is the environment i enter
Look at my picture the second post, at the far left vertical bar, it should look the same with the platformio and marlin adb installed as extension. Start empty by clicking on file left top, and select close folder. Click on the left vertical bar the Autobuild Marlin shortcut (assuming you have both abd marlin and platformio installed.) click on open a marlin 2.x Folder, select your folder wich contain you firmware like marlin2.1.2.5 as example. Wait a few seconds until platformio and the adb presenting themselves in separate tabs. Press again in the far left bar on the marlin adb button. Look at my picture in the beginning of this post, the green circle around the buttons are the buttons who are working, the red in the middle are broke. Read my other post if this fails, it clarify also what the adb extually is, you can build firmware without adb if necessary.
As reminder.... I had compile issues this morning when the firmware was not in the root of your drive, it must be than like c:\marlin2.1.2.5 or in my case d:\marlin2.1.2.5 Next reminder, select only a firmware folder with the root directly behind it, not a folder in a folder.
This issue was caused by a change in VSCode. The built-in browser DOM handler behind jQuery's .html() function now URL-encodes certain attribute values, meaning it now gives <env> where it used to give <env>.
Patching now…
Should've known that < and > inside of HTML attributes was eventually going to spit out < and > in some contexts. Now we have some insight into the inner workings of VSCode and Electron. https://github.com/microsoft/vscode/pull/278722