Re: [PLUG] serial communication with dmm (was com port in guest to usb in host (virtual box))
Have you measured the voltages on DTR and RTS during the runs? Try it with sigrok and with the vendor software and see if there is a difference in those values. On Thu, Dec 28, 2017 at 9:51 PM, Denis Heidtmann wrote: > This saga continues. > > On the laptop with a usb-serial adapter I got to the point where the > commands: > sigrok-cli --driver mastech-mas345:conn=/dev/ttyUSB0 --show > sigrok-cli --driver mastech-mas345:conn=/dev/ttyUSB0 --scan > sigrok-cli --driver mastech-mas345:conn=/dev/ttyUSB0 --samples 10 > > behave as expected except the last one returns no data. I was advised to > try using these same commands on the desktop which has an RS232 port, thus > removing the usb-serial adapter from the picture. Good idea. > > After just guessing what serial port to use, I run the following command: > > sigrok-cli --driver mastech-mas345:conn=/dev/ttyS0 --scan > The following devices were found: > mastech-mas345 - MASTECH MAS345 with 1 channel: P1 > > This is the same response I got on the laptop. > > sigrok-cli --driver mastech-mas345:conn=/dev/ttyS0 --show > mastech-mas345 - MASTECH MAS345 with 1 channel: P1 > Supported driver options: > conn > serialcomm > Supported configuration options: > > This is the same response I got on the laptop. > > sigrok-cli --driver mastech-mas345:conn=/dev/ttyS0 --samples 10 > > [no response except the usual ~10 second delay] > > This is the same response I got on the laptop. RATS! > > This eliminates the usb-serial device from the picture. > > Recall that when running --samples 10 command on the laptop I was able to > detect pulses on the serial line consistent (in a general sense) with a > response from the dmm. Also recall that running the mfg. sw under windows > on the desktop showed flawless communication. > > finally, I report: > stty -F /dev/ttyS0 -a speed 600 baud; rows 0; columns 0; line = 0; > intr = ; quit = ; erase = ; kill = ; eof = > ; > eol = ; eol2 = ; swtch = ; start = ; stop = > ; > susp = ; rprnt = ; werase = ; lnext = ; > discard = ; min = 0; time = 0; > -parenb -parodd -cmspar cs7 hupcl cstopb cread clocal -crtscts > -ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon > -ixoff > -iuclc -ixany -imaxbel -iutf8 > -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 > vt0 ff0 > -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop > -echoprt > -echoctl -echoke -flusho -extproc > > And the protocol is reported to be: > > data format: 7n2 at 600 baud (7 bits, no parity, 2 stop bits). > Control lines: >DTR and RTS lines are used to power the TX line: RTS is clear >for -12 supply; DTR is set for +12 supply. Data transmission is >solicited sending whatever character to the RX line. > > Any suggestions as to where to go from here? > > Thanks, > -Denis > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] serial communication with dmm (was com port in guest to usb in host (virtual box))
This saga continues. On the laptop with a usb-serial adapter I got to the point where the commands: sigrok-cli --driver mastech-mas345:conn=/dev/ttyUSB0 --show sigrok-cli --driver mastech-mas345:conn=/dev/ttyUSB0 --scan sigrok-cli --driver mastech-mas345:conn=/dev/ttyUSB0 --samples 10 behave as expected except the last one returns no data. I was advised to try using these same commands on the desktop which has an RS232 port, thus removing the usb-serial adapter from the picture. Good idea. After just guessing what serial port to use, I run the following command: sigrok-cli --driver mastech-mas345:conn=/dev/ttyS0 --scan The following devices were found: mastech-mas345 - MASTECH MAS345 with 1 channel: P1 This is the same response I got on the laptop. sigrok-cli --driver mastech-mas345:conn=/dev/ttyS0 --show mastech-mas345 - MASTECH MAS345 with 1 channel: P1 Supported driver options: conn serialcomm Supported configuration options: This is the same response I got on the laptop. sigrok-cli --driver mastech-mas345:conn=/dev/ttyS0 --samples 10 [no response except the usual ~10 second delay] This is the same response I got on the laptop. RATS! This eliminates the usb-serial device from the picture. Recall that when running --samples 10 command on the laptop I was able to detect pulses on the serial line consistent (in a general sense) with a response from the dmm. Also recall that running the mfg. sw under windows on the desktop showed flawless communication. finally, I report: stty -F /dev/ttyS0 -a speed 600 baud; rows 0; columns 0; line = 0; intr = ; quit = ; erase = ; kill = ; eof = ; eol = ; eol2 = ; swtch = ; start = ; stop = ; susp = ; rprnt = ; werase = ; lnext = ; discard = ; min = 0; time = 0; -parenb -parodd -cmspar cs7 hupcl cstopb cread clocal -crtscts -ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke -flusho -extproc And the protocol is reported to be: data format: 7n2 at 600 baud (7 bits, no parity, 2 stop bits). Control lines: DTR and RTS lines are used to power the TX line: RTS is clear for -12 supply; DTR is set for +12 supply. Data transmission is solicited sending whatever character to the RX line. Any suggestions as to where to go from here? Thanks, -Denis ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Am I asking the "right question"
'chroot' is an isolation/security mechanism. It doesn't allow programs running within it to access anything except the kernel and the programs/libraries within the chroot. For what you are doing, think of it as a file system tree that you can test most of your boot environment (short of booting) prior to needing to actually boot it. And because it is just a command away, it is fast to change and experiment. On Thu, Dec 28, 2017 at 8:13 AM, Richard Owlett wrote: > Those are among the pages that confused me long ago. > > They, without adequate background, say to use "chroot". > My visualization of using debootstrap is to place Debian on a write only > medium. > The descriptions of "chroot" I've seen imply it's a crude VM like thingy. > > > > On 12/28/2017 09:30 AM, David Bridges wrote: > >> Search for debootstrap, the link provided earlier was for an extremely >> old version of Debian although a search for dbootstrap debian | debian >> dbootstrap in search engines finds current documentation >> >> debootstrap wiki page >> https://wiki.debian.org/Debootstrap >> >> Current Debian install guide >> https://www.debian.org/releases/stable/amd64/index.html.en >> >> debootstrap section in current install guide >> https://www.debian.org/releases/stable/amd64/apds03.html.en#idm46300556 >> 432288 >> >> To me this doesn't really sound like what you are looking for but only >> you can know for sure. >> >> -- >> David >> >> > > > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Am I asking the "right question"
Those are among the pages that confused me long ago. They, without adequate background, say to use "chroot". My visualization of using debootstrap is to place Debian on a write only medium. The descriptions of "chroot" I've seen imply it's a crude VM like thingy. On 12/28/2017 09:30 AM, David Bridges wrote: Search for debootstrap, the link provided earlier was for an extremely old version of Debian although a search for dbootstrap debian | debian dbootstrap in search engines finds current documentation debootstrap wiki page https://wiki.debian.org/Debootstrap Current Debian install guide https://www.debian.org/releases/stable/amd64/index.html.en debootstrap section in current install guide https://www.debian.org/releases/stable/amd64/apds03.html.en#idm46300556 432288 To me this doesn't really sound like what you are looking for but only you can know for sure. -- David ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Am I asking the "right question"
Search for debootstrap, the link provided earlier was for an extremely old version of Debian although a search for dbootstrap debian | debian dbootstrap in search engines finds current documentation debootstrap wiki page https://wiki.debian.org/Debootstrap Current Debian install guide https://www.debian.org/releases/stable/amd64/index.html.en debootstrap section in current install guide https://www.debian.org/releases/stable/amd64/apds03.html.en#idm46300556 432288 To me this doesn't really sound like what you are looking for but only you can know for sure. -- David On Thu, 2017-12-28 at 08:55 -0600, Richard Owlett wrote: > On 12/26/2017 12:45 PM, Richard Owlett wrote: > > On 12/26/2017 10:48 AM, Carl Karsten wrote: > > [snip] > > > > > > https://www.debian.org/releases/potato/i386/ch-init-config.en.htm > > > l > > > "dbootstrap is the name of the program which is run after you > > > have booted > > > into the installation system. It is responsible for initial > > > system > > > configuration and the installation of the ``base system''. " > > I don't find "dbootstrap" in current Debian docs. However the > phrasing > is helping to reorganizing my thought patterns. > > > > > > > > Here is something close. > > > It contains just what is needed to install a minimal system, > > > (what it > > > sounds like you want) > > > and then it's > > > the late_command does stuff you might want too: > > > apt install git ansible > > > git clone playbook > > > ansible ... which installs and configures the apps needed to make > > > videos. > > > > > > This script creates a bootable usb stick based on a 58M > > > hd-media/boot.img.gz > > > https://github.com/CarlFK/video-stack-deploy/blob/nbpy/scripts/mk > > > _usb_installer.sh > > > > > > Most of the script is managing the ansible parameters. > > > > I'll have to spend some time with ansible to see what its goals and > > how > > the mesh with my mental image of my goals and the path to > > accomplish them. > > > > Your post caused me to modify my search terms. > That found recent debootstrap tutorial and reminded me of "dead > ends(?)" > from my past "debootstrap" searches. I've a reading assignment that > I > won't be able to start until next week." > > Thank you. > > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Am I asking the "right question"
On 12/26/2017 12:45 PM, Richard Owlett wrote: On 12/26/2017 10:48 AM, Carl Karsten wrote: [snip] https://www.debian.org/releases/potato/i386/ch-init-config.en.html "dbootstrap is the name of the program which is run after you have booted into the installation system. It is responsible for initial system configuration and the installation of the ``base system''. " I don't find "dbootstrap" in current Debian docs. However the phrasing is helping to reorganizing my thought patterns. Here is something close. It contains just what is needed to install a minimal system, (what it sounds like you want) and then it's the late_command does stuff you might want too: apt install git ansible git clone playbook ansible ... which installs and configures the apps needed to make videos. This script creates a bootable usb stick based on a 58M hd-media/boot.img.gz https://github.com/CarlFK/video-stack-deploy/blob/nbpy/scripts/mk_usb_installer.sh Most of the script is managing the ansible parameters. I'll have to spend some time with ansible to see what its goals and how the mesh with my mental image of my goals and the path to accomplish them. Your post caused me to modify my search terms. That found recent debootstrap tutorial and reminded me of "dead ends(?)" from my past "debootstrap" searches. I've a reading assignment that I won't be able to start until next week." Thank you. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
