Getting an error in lightburn

[Jeffjake (Jeff Jacobson)]

I just got a Enjoywood 20w (Atomstack 20) and was using the free trial for a few days with no problem. Now, it maybe will engrave a few lines, sometimes 3 or 4 minutes and just stop. I get the below log. I tried lasergrbl which works fine. I do not want to learn lasergrbl. Here is the log, if you can help that would be great!

Guru Meditation Error: Core 1 panic’ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x400854e8 PS : 0x00060a30 A0 : 0x800eb156 A1 : 0x3ffb1dc0
A2 : 0x0f237adc A3 : 0x00000000 A4 : 0x00000000 A5 : 0x00000064
A6 : 0x00060a20 A7 : 0x00000000 A8 : 0x800861f6 A9 : 0x00000000
A10 : 0x0efffffb A11 : 0x00060a23 A12 : 0x00000050 A13 : 0xefffffff
A14 : 0x0efffffb A15 : 0x00000000 SAR : 0x00000002 EXCCAUSE: 0x0000001c
EXCVADDR: 0x800eb4d6 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xfffffffe
ELF file SHA256: 0000000000000000
Backtrace: 0x400854e8:0x3ffb1dc0 0x400eb153:0x3ffb1de0 0x400d8ab4:0x3ffb1e00 0x400d48f9:0x3ffb1f70 0x400d2f73:0x3ffb1f90 0x4010f274:0x3ffb1fb0 0x4008ca52:0x3ffb1fd0
Rebooting…
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x1b (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5856
entry 0x400806a8
Grbl 1.1h [‘$’ for help]
[MSG:Local access point Engraver_16514 started, 192.168.4.1]
[MSG:HTTP Started]
[MSG:TELNET Started 8080]
[MSG:Check limits]
[MSG:‘$H’|‘$X’ to unlock]
Grbl 1.1h [‘$’ for help]
[MSG:‘$H’|‘$X’ to unlock]
[MSG:Caution: Unlocked]
ok

[misken (Melvin)]

Looks like a bad firmware. Do you get this messages after the crash or at the beginning? If it’s at the beginning, that doesn’t matter. If it happens during runtime, flash the firmware again.

[Jeffjake (Jeff Jacobson)]

I will do that. It does print perfectly with lasergrbl.

[misken (Melvin)]

That’s a little weird, indeed. You can also try to toggle the “enable DTR signal” option in device settings, this also helps with communication problems sometimes. And disable gcode clustering in case it is turned on.