-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task on core 1 crashes if USB based console output is used #88
Comments
I apologize - I didn't initialize the console hooks for the first core 1 task started. Somehow I managed to not notice this until now, probably because in my testing I was always testing with the second core 1 task started for whatever reason. The fix is now in the Travis |
What is strange about this is that I am very sure I tested this multiple times in the past, and yet I am having trouble finding whether this code had gotten removed at some point in the past... |
It's annoying when that happens! |
I think I figured out what happened ─ I previously had code that initialized peripherals on core 1, and it must have set up the console hooks for USB amongst other things, but when I removed this code as I had found it to cause issues, I forgot to add the console hooks for when core 1 was just started. BTW, I'm making a new build, build 1.5.0.1, right now that will contain this fix. |
Release 1.5.0.1, which fixes this issue, is now out. |
I tried running tasks on core 1 but they failed badly. Some experiments show that "emit" crashes if the USB console is used. If I redirect console output to the UART it works fine.
The text was updated successfully, but these errors were encountered: