lwc:hardware:beagle

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
lwc:hardware:beagle [2026/06/05 15:35] – John Harrisonlwc:hardware:beagle [2026/06/06 06:38] (current) – John Harrison
Line 14: Line 14:
     * this code with examples shows how to format everything for LEDScape     * this code with examples shows how to format everything for LEDScape
  
-=== Patches/Fixes ===+=== Patches/Fixes/Gotchas ===
   * LEDScape (at least the Geocene version of it) uses 100% CPU   * LEDScape (at least the Geocene version of it) uses 100% CPU
     * the issue is the DMX-over-network protocol is failing. If not using DMX then remove it     * the issue is the DMX-over-network protocol is failing. If not using DMX then remove it
Line 25: Line 25:
       * //change survives reboot//       * //change survives reboot//
   * for some reason ''mpg123-jack'' segfaults (most, not all the time) when LEDScape is running. Other JACK clients and the JACK server seem OK.   * for some reason ''mpg123-jack'' segfaults (most, not all the time) when LEDScape is running. Other JACK clients and the JACK server seem OK.
 +  * even when the # of strands is 1, it seems many of the pins in the P8 header are not usable when LEDScape/opc-server is running. An exception is GPIO 61 which seems to work fine regardless.
 +
 ==== Connecting ==== ==== Connecting ====
   * The bone is running a DHCP client so if you run a DHCP server it will get assigned an IP address   * The bone is running a DHCP client so if you run a DHCP server it will get assigned an IP address
  • lwc/hardware/beagle.txt
  • Last modified: 2026/06/06 06:38
  • by John Harrison