Closed Bazmundi closed 1 year ago
Yep, just blues due to restarting the setup after a long time. With the create agent installed, wcc picks up the board without crashing. Recommend something more graceful, since this probably just needs to drop out calmly and report that the create-agent is not running.
I recently built wcc from source on Win10: wcc.zip Does the crash also happen with this version?
mine still crashes with this version:
C:\Users\sethe\Downloads>wcc -p COM6 -f
panic: Invalid arguments were passed to the function [recovered]
panic: Invalid arguments were passed to the function [recovered]
panic: Invalid arguments were passed to the function
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x7ff62738522d]
goroutine 1 [running]:
github.com/whitecatboard/whitecat-console/vendor/github.com/mikepb/go-serial.(*Port).Close(0x0, 0x1, 0x1)
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/vendor/github.com/mikepb/go-serial/serial.go:507 +0x2d
main.(*Board).detach(0xc00009c2c0)
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/board.go:313 +0xf1
main.main.func1()
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/main.go:93 +0xd1
panic(0x7ff6275b0960, 0x7ff627556eb0)
c:/go/src/runtime/panic.go:679 +0x1c0
main.connect.func1()
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/connection.go:56 +0xf8
panic(0x7ff6275b0960, 0x7ff627556eb0)
c:/go/src/runtime/panic.go:679 +0x1c0
main.(*Board).attach.func1(0xc00009c2c0)
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/board.go:259 +0x181
panic(0x7ff6275b0960, 0x7ff627556eb0)
c:/go/src/runtime/panic.go:679 +0x1c0
main.(*Board).attach(0xc00009c2c0, 0xc000040cb0)
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/board.go:279 +0x379
main.connect(0xc00000a0d0, 0x4)
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/connection.go:79 +0x1a3
main.main()
C:/Users/Thomas/go/src/github.com/whitecatboard/whitecat-console/main.go:266 +0x6a3
I receive the same error when I use a COM port that doesn't exist.
Could this also occur if the board is broken? I'm not 100% confident that it works
Yes, that probably would be the exact result. Assuming the board is broken, closing the issue. Feel free to open a new issue in the wcc repo in case of problems.
Running Windoze 10 and hanging ESP32 board off COM9.
Understanding wcc is a separate project but because the destructions followed were from this project.
Installed pre-compiled wcc binary as per destructions, including wcc to c:\windows\system32, resulting in the following (when run from wherever):
Very good! But, with a board hanging off COM9:
And of course, still with a board hanging off COM9:
That's all with the board connected. Without the board connected to COM9, I get:
Note, COM9 does not appear in list since when the board is on, wcc crashes.
The board type is a DIYMORE. I have 3 of the boards.
I had previously had the lua-rtos system running on all the boards at least a 18 months ago. I had since downed tools on a project, and in the meantime replaced by PC with a laptop and am now getting set up for lua-rtos again (or maybe not). Whether that means there is a update to wcc that now has a problem is a question?
The boards definitely come up in my devices list under Windoze. I have bombed one with Arduino blink to check it out, so I have drivers for the boards (obviously) and can talk to them.
Happy to hear I need the create agent, but whenever I click the link, nothing happens (IGNORE as this seems to be a problem with CHROME, but EDGE seems fine).