QEMU serial port suggestion

 

A fellow on Facebook suggested the following to create a serial port (virtual) to telnet into on a QEMU host emulation.  

Running a sparc host running Solaris 2.8 or Sunos 4.1 as guests with sparc versions on the qemu host.  Networking isn't functional yet, but would be nice to get into the system remotely somehow till it does.  

This emulates a serial port on a virtual Sparc system so won't natively have any networking.  Hopefully will discover how to get the sparc host NIC connected on the guest, but this is handy for now.

Adam Koerner
Jim St Add "-serial telnet:localhost:4321,server,nowait". Then you can just telnet to the 4321 port

--30--

Beaglebone Black Wifi (and others) Serial port notes

Some info from another site on the serial ports.

The BeagleBone Black 1 has 6 on-board serial ports 3.3V TTL.

On the BeagleBone Black, it’s only the /dev/ttyO0 that is enabled by default, and it is coupled to the serial console. The other serial ports must be enabled before they can be used.

There is useful information about the serial ports of the BeagleBone in this link 2.


The BeagleBone Black Wireless is Bluetooth 4.1 compatible which is normally compatible with Bluetooth 4.0. Therefore, you should be able to use this 4.0 Bluetooth BLE Link Bee 1 with the SSC32.

some sources:

video with some app, maybe for below link

https://www.robotshop.com/en/easydriver-stepper-motor-controller.html

https://github.com/derekmolloy/beaglebone



--30--

Orange Pi Zero serial port

Orange Pi Zero ports in the small cube system have a serial port on the power port (micro USB) as well as power.

The only thing I've found so far says that the baud rate is 115200 baud.  On the linux system I hooked it to turned out to connect at 9600 baud.

http://www.orangepi.org/Docs/LogintotheOrangePi.html

Otherwise this note on connecting (I'm guessing they didn't use an RPI 3+) to another SOC board is okay.

minicom connects fine.

The other note on the raspian system running on the RPI 3+ is that the device is /dev/ttyAMA0

Also, have not figured out how to get the current raspian to come up on this system w/o a network cable attached.

Wifi is connected manually with the cli interface instructions elsewhere and works once up.  But from a power on, the system is stuck somewhere with no console or other output on the ttyAMA0 port to indicate what is stuck.

and if one lets the orangepizero come to an end (blinking that is on the RJ45 ports, plugging in a live network doesn't get it to continue to successful boot.

Bluetooth serial Raspberry Pi 3

set up raspberry pi 3 bluetooth to allow serial connection once paired.

https://hacks.mozilla.org/2017/02/headless-raspberry-pi-configuration-over-bluetooth/

Basic part of above which covers setting up bluetooth connection.  No pass code, all parings accepted.

rfcomm connects and presents a shell session on connection w/o password, so more can be done to secure this.

You’ll create this file in the /home/pi directory, like so:

$ sudo nano /home/pi/btserial.sh

Add the following lines to the script:

#!/bin/bash -e

#Edit the display name of the RaspberryPi so you can distinguish
#your unit from others in the Bluetooth console
#(very useful in a class setting)

echo PRETTY_HOSTNAME=raspberrypi > /etc/machine-info

# Edit /lib/systemd/system/bluetooth.service to enable BT services
sudo sed -i: 's|^Exec.*toothd$| \
ExecStart=/usr/lib/bluetooth/bluetoothd -C \
ExecStartPost=/usr/bin/sdptool add SP \
ExecStartPost=/bin/hciconfig hci0 piscan \
|g' /lib/systemd/system/bluetooth.service

# create /etc/systemd/system/rfcomm.service to enable 
# the Bluetooth serial port from systemctl
sudo cat <<EOF | sudo tee /etc/systemd/system/rfcomm.service > /dev/null
[Unit]
Description=RFCOMM service
After=bluetooth.service
Requires=bluetooth.service

[Service]
ExecStart=/usr/bin/rfcomm watch hci0 1 getty rfcomm0 115200 vt100 -a pi

[Install]
WantedBy=multi-user.target
EOF

# enable the new rfcomm service
sudo systemctl enable rfcomm

# start the rfcomm service
sudo systemctl restart rfcomm

Save the file, and then make it executable by updating its permissions like so:

$ chmod 755 /home/pi/btserial.sh

Now you have the basics of the script required to turn on the Bluetooth service and configure it.  But to do this 100% headless, you’ll need to run this new script on startup. Let’s edit /etc/rc.local to launch this script automatically.

$ sudo nano /etc/rc.local

Add the following lines after the initial comments:

#Launch bluetooth service startup script /home/pi/btserial.sh
sudo /home/pi/btserial.sh &

Save the rc.local script, unmount the image, and write it to an SD Card using your favorite tool (mine is ApplePiBaker).
Now you are ready to go.  Plug in power to the Rpi and give it 30 seconds or so to startup. Then unplug it, and plug it in again and let it boot up a second time.  Restarting the Bluetooth service doesn’t work correctly, so we need to reboot.
-30-

vmware serial ports (on guests)

utility for configuring or connecting to ports

http://communities.vmware.com/message/1741943

quote:

As far as I could gather, there is/was no easy way to do what I wanted to do.  That said, I was able to cobble together a solution.

First of all, VMware sells an additional license called the "Remote Virtual Serial Port Concentrator" license (for way too much money, IMO) per ESXi server, which is what allows one to pipe a virtual machine's serial port out to a telnet port, using a telnet daemon running on the ESXi server.  Paying the money and getting this license was the first step.  Thankfully, VMware's turnaround was quick enough after we paid the money, that we were able to install these permanent licenses before the temporary, evaluation licenses expired.

The next step was to dynamically configure this serial port for my virtual machines.  I could find no VMware-supplied API's, so I hacked my own perl script.  I've attached it in case others find it useful, warts and all.  I put in lots of comments since I was learning how to do this and I'm sure there's extra junk in there that's not needed, but it's working for me.  Use at your own risk.

Attachments:

• VMSerialPort.perl (36.7 K)  

server firewall:

configure->security profile has remote port to add in gui

http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.vmadmin.doc_41/vsp_vm_guide/configuring_virtual_machines/t_change_the_serial_port_configuration.html

configuring virtual serial port

http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%2FGUID-A779C84D-4324-4D32-AF43-BBD962ABC9E3.html

vSPC page:

http://isnotajoke.com/vmware_virtual_serial_ports.html

vSPC home:

http://sourceforge.net/p/vspcpy/home/Home/

vmware vSPC info:
http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/vsp41_usingproxy_virtual_serial_ports.pdf