Another option can be adding little P-chanel FET as an inverter. I guess if one doesn’t have stock of random parts then purchase of the FET is more trouble than just getting STLink. But then also convenience of never need to open that case again for flashing… Hmm…
Kind of wash for me.
How many screws does the ON/OFF cover panel really need anyways? LOL
Well I’ll be a money’s uncle. $22 is not really a boolean. Seems $22=9 is a solution for the negative coordinates of stock grbl.
Is that perhaps a grblHAL mod? Not certain but I don’t think this concept of homing cycle flags exists in standard GRBL.
it probably is since the description which said it was a bool also said to look at config.h for advanced settings.
Not in typical GRBL.
Very interesting!
I’ve tried to write “9” to it. Read returned “1”.
I got to compare sources.
The developer who’s been communicating with me on my port is a CNC user of grblHAL so I’m seeing things being developed in grblHAL more than just porting updates.
I have the grblHAL firmware working on the JL2 laser engraver now also. I burned the firmware using the stock USB cable, a jump wire and STM32CubeProgrammer.
grbl settings changes:
Homing direction needed to be reversed
Max X = 150, $130=150
Max Y = 240, $131=240
Setting $22=9 corrected the negative coordinate space issue of stock grbl so no G54 offset
I exported my grbl settings in LightBurn and attached them if anyone cares to want to look.
LightBurn-MachineSettings-JL2.lbset (5.9 KB)
Do you have the code somewhere I can get at it?
sent via PM until I get more testing on it. I’d thought the grbl defaults would have been set for the JL1 but they were not. I manually updated them then tested with LightBurn and then exported from LightBurn so should be a good v1.0 release.
Is that the settings in post 138?
not likely since I just found out about $22=9 the other night and I just setup the JL2 today.
Ortur has finally posted their source code after being called out for violating the GPL. So not only STM32F103 grbl32 v1.1d( builds out of the box ) but also their bootloader which presents a 64K USB thumb drive which you copy the firmware.bin file onto and then reboot. The bootloader looks for the firmware.bin file and if it’s found installs it then runs it, otherwise it just runs what’s already loaded.
It’s a nice bootloader with only one failing immediately observed and that is it requires FAT32 directory naming of the firmware.bin file which requires Mac and Linux users to use MTOOLS package mcopy util to copy and set the secondary directory name. Otherwise a handy bootloader.
We finally know where the user app is stored.
“user application will be flashed to 0x08004000”
Cool!
Bot I cannot find precompiled boot loader?
Is there any compiled stuff or all raw?
HN,
No, we don’t. This is not the same boot loader. First of all JL1 whole thing fitting 64K, including boot loader and app BIN. This boot loader alone is 64K. Then JL1 also scrambled.
I just tried to boot and checked for emulated driver - nope.
Considering that most JL1 are 128K - it is a nifty bootloader to use.
I wouldn’t call it raw, there are the Eclipse CDT project files( .project ) and I imported the STM32 based firmware into STM32CubeIDE and it built with just a few warnings.
I have not tried to compile the bootloader yet.
no, it’s much smaller and presents a virtual drive of ~64K to the host system connected. The v1.1d firmware built to 54K
I just built it and it’s ~14K and also looked at the Bootloader v1.0 docx file and now I see the magic… it references a SPI Flash memory module. So maybe this creates the USB disk on the SPI Flash and copies it into native-onboard flash when found to exist. Doesn’t help us here but a cool bootloader just the same.
I also translated the latest comments seen in the repo which clearly say “Mac, Linux” and it appears they fixed the VFAT second directory entry issue which required users to copy the firmware.bin file using MTOOLS mcopy on Mac and Linux.
Sal, Doug,
Thanks so much for your efforts. Today I was able to use the SL-Link to program my JL1 boar with the current version on the git. I can talk via Putty and the next step is to put it all back together and try Lightburn again.
Thanks you guys,
Mike Bamberg
Mike, are you saying you updated the Ortur Grbl32 1.1d to the JL1 machine and have it functional?
