-
Notifications
You must be signed in to change notification settings - Fork 59
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
WS2811 in tinkerboard #165
Comments
What hardware are you using? What O/S? |
Tinkerboard R2.0 and tinker OS rockchip 3288.. |
Duplicate of #163 |
sample code using spi mode or any other material to use with spi mode ?? |
Yes, there is sample code for SPI Mode - see the sampleapps folder in the diozero-ws281x-java project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Loaded library 'ws281xj' from classpath
ws2811_init failed: Hardware revision is not supported
Error: java.lang.RuntimeException: Error initialising the WS281x strip
java.lang.RuntimeException: Error initialising the WS281x strip
at com.diozero.ws281xj.rpiws281x.WS281x.(WS281x.java:171)
at com.diozero.ws281xj.rpiws281x.WS281x.(WS281x.java:138)
at com.mycompany.App.main(App.java:23)
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x92e1f4bc, pid=6680, tid=6696
JRE version: OpenJDK Runtime Environment (11.0.18+10) (build 11.0.18+10-post-Debian-1deb10u1)
Java VM: OpenJDK Server VM (11.0.18+10-post-Debian-1deb10u1, mixed mode, g1 gc, linux-)
Problematic frame:
C [libws281xj7417783119458007225.so+0x24bc] ws2811_fini+0xc
No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
An error report file with more information is saved as:
/home/linaro/mydiozeroproject/hs_err_pid6680.log
If you would like to submit a bug report, please visit:
https://bugs.debian.org/openjdk-11
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
The text was updated successfully, but these errors were encountered: