Hi Jason, Thanks for the message. I configured the pins, and confirmed it works using the screen command as below. Does that mean that the two pins are ready as the serial pins where I can transfer data with different baud-rates? ---------------------------------------- config-pin p9.13 uart config-pin p9.11 uart screen /dev/ttyO4 -- confirm it works --------------------------------------- Thank you,
LLD On Mon, Oct 1, 2018 at 12:54 PM Jason Kridner <[email protected]> wrote: > On Fri, Sep 28, 2018 at 1:40 PM <[email protected]> wrote: > >> Hi All, >> I am a new bee in BBB too, but have some knowledge about the serial >> device and data-acquisition. I have read all the emails below, and >> understood the code. The problem is the command to link the UART4 to >> /dev/tty failed. >> >> debian@beaglebone:/var/lib/cloud9$ echo BB-UART4 > /sys/devices/bon >> e_capemgr9/slots >> bash: /sys/devices/bone_capemgr9/slots: No such file or directory >> > >> >> Cannot find the bone_capemgr in the /sys/devices in this board. Please >> advice. >> > > For newer images, capemgr is no longer supported as a kernel service. > Instead, the 'config-pin' utility is used to enable pins to provide access > to a UART. > > Try: > > config-pin p9.13 uart > config-pin p9.11 uart > > > It is still possible to use the bootloader (u-boot) based capemgr via > /boot/uEnv.txt, but I don't recommend it as it is error prone and far less > flexible. > > It is also possible to utilize the mainline device tree overlays, but that > process is also error prone and less than intuitive. > > Please report back on your success with config-pin. > > >> >> ls -l /sys/devices/ >> total 0 >> drwxr-xr-x 5 root root 0 Sep 28 17:22 armv7_cortex_a8 >> drwxr-xr-x 3 root root 0 Sep 28 17:22 breakpoint >> drwxr-xr-x 22 root root 0 Sep 28 17:22 platform >> drwxr-xr-x 3 root root 0 Sep 28 17:22 soc0 >> drwxr-xr-x 3 root root 0 Sep 28 17:22 software >> drwxr-xr-x 6 root root 0 Sep 28 17:22 system >> drwxr-xr-x 3 root root 0 Sep 28 17:22 tracepoint >> drwxr-xr-x 12 root root 0 Sep 28 17:22 virtual >> >> Lingling >> >> >> On Thursday, March 27, 2014 at 4:59:00 PM UTC-4, Mark A. Yoder wrote: >>> >>> Nick: >>> I have some bonescript code that works with the UART, but I'm not >>> using the built-in bonescript calls. It works fine with a GPS, though I >>> don't use it to transmit. >>> >>> I took would like to see an example that uses the bonescript calls. >>> Before ruing the code you need to: >>> >>> beagle# *npm install -g serialport* >>> >>> beagle# *echo BB-UART4 > /sys/devices/bone_capemgr.*/slots* >>> >>> --Mark >>> #!/usr/bin/env node >>> // From: https://github.com/voodootikigod/node-serialport >>> // From: https://github.com/jamesp/node-nmea >>> >>> var b = require('bonescript'); >>> var nmea = require('nmea'); >>> >>> //console.log(b.serialOpen); >>> >>> //var sp = b.serialOpen('/dev/ttyO4', {baudrate: 9600} ); >>> // parser: b.serialParsers.readline("\n")}); >>> >>> >>> var serialport = require("serialport"); >>> var SerialPort = serialport.SerialPort; // localize object constructor >>> >>> var sp = new SerialPort("/dev/ttyO4", { >>> parser: serialport.parsers.readline("\n") >>> }); >>> >>> sp.on("data", function (data) { >>> console.log("here: "+data); >>> console.log(nmea.parse(data)); >>> }); >>> >>> >>> On Thursday, December 19, 2013 1:49:30 AM UTC-5, Nick Farrell wrote: >>>> >>>> I am a newbie to BeagleBone Black(BBB) but have good knowledge about >>>> Arduino. I would like to know how to open a serial port in BBB using the 4 >>>> UARTs available in BBB using BoneScript library and use cloud9 ide to see >>>> the serial data on the console. Can anyone help me on this issue. >>>> >>> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/c5d7fc58-966c-44c0-ac67-2d9c3d5a6590%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/c5d7fc58-966c-44c0-ac67-2d9c3d5a6590%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > https://beagleboard.org/about > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/r1jMChzokaM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPk4j3Ks%2BwSFsMtVCvfRftMdwqjoTSRZxk40Q2O%3DA8Ms3A%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPk4j3Ks%2BwSFsMtVCvfRftMdwqjoTSRZxk40Q2O%3DA8Ms3A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALDec5xFppNOhxei3cqfbkiVEsvx2d9avQHA12gs2JFg9Mywyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
