> > *think its pretty sweet to have node-red running "out of the box" but > without the BoneScript access to the GPIO and A/D pins (I assume BoneScript > PWM is still broken) its nowhere near as neat as it could be!* >
So, why don't you learn how to do this without using Bonescript ? It's not that hard, but is not exactly something that is easily relate-able via email either. But I'll try . . . What I did was . . . - start from a fresh bare image, but for simplicity a console image would work fine too. - downloaded, and installed development prerequisites. Including git. - downloaded Nodejs code via git, compiled, and installed once finished compiling. - Learned a bit of how to access files from Nodejs . . . and all set . . .done. On Tue, Feb 2, 2016 at 3:16 PM, Robert Nelson <[email protected]> wrote: > On Tue, Feb 2, 2016 at 3:57 PM, Robert Nelson <[email protected]> > wrote: > > On Tue, Feb 2, 2016 at 3:39 PM, Wally Bkg <[email protected]> wrote: > >> I think its pretty sweet to have node-red running "out of the box" but > >> without the BoneScript access to the GPIO and A/D pins (I assume > BoneScript > >> PWM is still broken) its nowhere near as neat as it could be! > > > > GPIO & A/D can be accessed via config-pin > > > > root@beaglebone:~# config-pin -l P9.18 > > default gpio gpio_pu gpio_pd spi i2c pwm > > > > > >> > >> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript > >> working beyond installing the Beaglebone nodes with npm? > > > > sudo apt-get install linux-image-3.8.13-bone79 > > sudo reboot > > > > Bonescript is installed.. > > > >> I'm having issues with this image getting the "gadget" to connect -- it > >> seems to only work from a cold start -- when I first plug it in the FAT > >> partition mount but the gadget hangs "waiting for IP address" If I > press > >> reset it may or may not start after the reboot. So far its always > started > >> if I hold the powerbutton down until it shuts off, and then press it > again > >> to do a cold boot. > > > > Okay, that's different.. Starts flashing the clean image to do reset > > button testing. ;) > > > > journalctl -f | grep kernel > > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: Attached scsi generic sg1 > type 0 > > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] 81920 512-byte > > logical blocks: (41.9 MB/40.0 MiB) > > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write Protect is off > > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Mode Sense: 0f 00 00 00 > > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write cache: enabled, > > read cache: enabled, doesn't support DPO or FUA > > Feb 02 15:52:54 hades kernel: sdb: sdb1 > > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Attached SCSI removable > disk > > push reboot... > > Feb 02 15:53:53 hades kernel: usb 5-1.4: USB disconnect, device number 8 > > Feb 02 15:53:53 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92: > > unregister 'rndis_host' usb-0000:00:10.1-1.4, RNDIS device > > Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronizing SCSI cache > > Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronize Cache(10) > > failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK > > Feb 02 15:54:18 hades kernel: usb 5-1.4: new high-speed USB device > > number 9 using xhci_hcd > > Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device found, > > idVendor=1d6b, idProduct=0104 > > Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device strings: > > Mfr=3, Product=4, SerialNumber=5 > > Feb 02 15:54:18 hades kernel: usb 5-1.4: Product: BeagleBoneBlack > > Feb 02 15:54:18 hades kernel: usb 5-1.4: Manufacturer: Circuitco > > Feb 02 15:54:18 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103 > > Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 eth0: register > > 'rndis_host' at usb-0000:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92 > > Feb 02 15:54:18 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device > > Feb 02 15:54:18 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage > > device detected > > Feb 02 15:54:18 hades kernel: scsi host16: usb-storage 5-1.4:1.4 > > Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92: > > renamed from eth0 > > Feb 02 15:54:18 hades kernel: IPv6: ADDRCONF(NETDEV_UP): > > enx7c669d4bac92: link is not ready > > Feb 02 15:54:19 hades kernel: scsi 16:0:0:0: Direct-Access Linux > > File-Stor Gadget 0401 PQ: 0 ANSI: 2 > > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: Attached scsi generic sg1 > type 0 > > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] 81920 512-byte > > logical blocks: (41.9 MB/40.0 MiB) > > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write Protect is off > > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Mode Sense: 0f 00 00 00 > > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write cache: enabled, > > read cache: enabled, doesn't support DPO or FUA > > Feb 02 15:54:19 hades kernel: sdb: sdb1 > > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Attached SCSI removable > disk > > yank power.... > > Feb 02 15:54:39 hades kernel: usb 5-1.4: USB disconnect, device number 9 > > Feb 02 15:54:39 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92: > > unregister 'rndis_host' usb-0000:00:10.1-1.4, RNDIS device > > Feb 02 15:54:39 hades kernel: sd 16:0:0:0: [sdb] Synchronizing SCSI cache > > Feb 02 15:54:39 hades kernel: sd 16:0:0:0: [sdb] Synchronize Cache(10) > > failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK > > Feb 02 15:55:07 hades kernel: usb 5-1.4: new high-speed USB device > > number 10 using xhci_hcd > > Feb 02 15:55:07 hades kernel: usb 5-1.4: New USB device found, > > idVendor=1d6b, idProduct=0104 > > Feb 02 15:55:07 hades kernel: usb 5-1.4: New USB device strings: > > Mfr=3, Product=4, SerialNumber=5 > > Feb 02 15:55:07 hades kernel: usb 5-1.4: Product: BeagleBoneBlack > > Feb 02 15:55:07 hades kernel: usb 5-1.4: Manufacturer: Circuitco > > Feb 02 15:55:07 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103 > > Feb 02 15:55:07 hades kernel: rndis_host 5-1.4:1.0 eth0: register > > 'rndis_host' at usb-0000:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92 > > Feb 02 15:55:07 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device > > Feb 02 15:55:07 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage > > device detected > > Feb 02 15:55:07 hades kernel: scsi host17: usb-storage 5-1.4:1.4 > > Feb 02 15:55:07 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92: > > renamed from eth0 > > Feb 02 15:55:07 hades kernel: IPv6: ADDRCONF(NETDEV_UP): > > enx7c669d4bac92: link is not ready > > Feb 02 15:55:08 hades kernel: scsi 17:0:0:0: Direct-Access Linux > > File-Stor Gadget 0401 PQ: 0 ANSI: 2 > > Feb 02 15:55:08 hades kernel: sd 17:0:0:0: Attached scsi generic sg1 > type 0 > > Feb 02 15:55:08 hades kernel: sd 17:0:0:0: [sdb] 81920 512-byte > > logical blocks: (41.9 MB/40.0 MiB) > > Feb 02 15:55:08 hades kernel: sd 17:0:0:0: [sdb] Write Protect is off > > Feb 02 15:55:08 hades kernel: sd 17:0:0:0: [sdb] Mode Sense: 0f 00 00 00 > > Feb 02 15:55:08 hades kernel: sd 17:0:0:0: [sdb] Write cache: enabled, > > read cache: enabled, doesn't support DPO or FUA > > Feb 02 15:55:08 hades kernel: sdb: sdb1 > > Feb 02 15:55:08 hades kernel: sd 17:0:0:0: [sdb] Attached SCSI removable > disk > > > > humm, really no difference here.. can you do the same with your device? > > Okay, now this is weird.. > > Testing the white, same as the black.. Start testing the green.. > > The "reset" button doesn't 100% work... Except when i want it to fail to > work.. > > seems like a slight delay... (looking at serial debug, while hitting reset) > > yet still usb/gadget/mass/acm comes up every time.. > > running: 4.3.0-1-amd64 on my host.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
