How to fix the stuck after the command, 'bash flash.sh' - bash

I was trying to flash the mendel-enterprise-chef-13 to the Coral EdgeTPU Development Board but got stuck after the command, "bash flash.sh."
The host computer is the MacBook Pro (2018) with macOS Mojave ver. 10 and connected with the Coral EdgeTPU Dev Board.
I have followed the instructions on the Coral Document listed at https://coral.withgoogle.com/docs/dev-board/get-started/.
The process went smooth up to without the problem untill the step 8 and 12.
mkdir -p ~/.local/bin
sudo mv ~/Downloads/platform-tools/fastboot ~/.local/bin/
pip3 install --user mendel-development-tool
and then install the CP210x USB to UART Bridge Virtual COM Port (VCP) driver for Mac.
screen /dev/cu.SLAB_USBtoUART 115200
fastboot 0
fastboot devices
1b0741d6f0609912 fastboot # I did not get this message
cd ~/Downloads
curl -O https://dl.google.com/coral/mendel/enterprise/mendel-enterprise-chef-13.zip
unzip mendel-enterprise-chef-13.zip \
&& cd mendel-enterprise-chef-13
bash flash.sh # Got stuck here.
I want to know how to fix the issues of flashing the mendel image.

this sounds like a problem with the USB-A USB-C cable, or the usb port on your host machine, have you tried a different port?

Related

Dockerize react-native dev environment & connect Android device to WSL2

I want to dockerize my react native development environment. Currently I have windows on my laptop, and I don't have the option to change that. I also have WSL2 installed and I started to build my dockerfile from this image
I also want to use my device, so I have to somehow connect the container (the docker runs actually in WSL2) with my android device. The WSL2 don't support USB devices (that are connected to the host windows system) currently so I was thinking about setting up a wireless adb connection on the local network but since my android is <11 I have to do some initial setup which requires me to connect adb over USB which is due to the reasons above, not possible... I don't want to use an USB server. Any ideas?
Assuming you have the whole dev-environment setup and working on linux/wsl, you can use socat to relay requests from wsl2 to adb on windows. You may have to deal with some firewall issues, but this works for me:
On Windows:
Run adb -a -P 5037 nodaemon server (credit to this redditor)
In another terminal, run adb devices to ensure your device is properly connected over usb.
On linux/wsl2:
Run socat -d -d TCP-LISTEN:5037,reuseaddr,fork TCP:$(cat /etc/resolv.conf | tail -n1 | cut -d " " -f 2):5037 (credit to this gist)
If you are developing for android with react-native and need to launch the metro bundler, you will need to open a port for the metro bundler on your windows firewall. I will assume you are using port 8081.
Run as administrator in powershell (Windows):
$WSL_CLIENT = bash.exe -c "ip addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}'"
iex "netsh interface portproxy add v4tov4 listenport=8081 listenaddress=127.0.0.1 connectport=8081 connectaddress=$WSL_CLIENT"
You should now be able to deploy your project to andriod.
On linux/wsl2:
npx react-native start
npx react-native run-android
If this doesn't work, the credited sources for steps (1) and (3) provide similar methods for achieving this. If you make a docker image, please share it here!

Gazebo stuck at loading your world

https://i.imgur.com/hYf1Bes.jpgm
I am trying to set up ROS and Gazebo in a VM running Ubuntu.
The goal is that I want to simulate Turtlebot with the open manipulator.
I installed everything without any issues.
Though I am not able to launch the Turtlebot environment on Gazebo (like here: http://emanual.robotis.com/docs/en/platform/turtlebot3/simulation/)
$roslaunch turtlebot3_fake turtlebot3_fake.launch
results in Gazebo staying forever in the state loading your world. After some time, it stops responding.
Launching the empty world however works.
I am using ROS 1 with Gazebo 7.0
My hardware setup:
MacBook Pro 13" 2019 with 16 GB RAM
Parallels VM: 3D virtual. ON, no performance limit, 4 CPU kernels, 12 GB RAM enabled
Thank you so much for your help.
After every change you made source your bash and make sure to run :
catkin make
if you've done this already then check if ros is installed properly by running
roscore
on one terminal and let it stay running.
After that try to launch your turtlebot on another terminal.
If it doesnt work even you have installed all of the needed things, i think the problem is with your VM, id recommend you to run ROS on Ubuntu running USB Stick.
cd ~/.gazebo/
mkdir models
cd models/
wget http://file.ncnynl.com/ros/gazebo_models.txt
wget -i gazebo_models.txt
ls model.tar.g* | xargs -n1 tar xzvf
try this gazebo try to download to packages that's why it waits u need internet for that this may take few mins

IPX Networking with DOS and DOSBox (under Raspbian)

My long-term-goal is to get Doom (version 1.1) running in 3 screen mode on a mix of hardware (1 x Pentium 3 under DOS 7.10 and 2 x Raspberry Pis under Raspbian).
I have DOS running LNE100TX (I can share the configuration files if that is helpful).
I enabled IPX in the configuration file started DOSBox under Raspbian.
[ipx]
# ipx: Enable ipx over UDP/IP emulation.
ipx=true
pi#raspberrypi:~$ dosbox
DOSBox version 0.74
Copyright 2002-2010 DOSBox Team, published under GNU GPL.
---
CONFIG:Loading primary settings from config file /home/pi/.dosbox/dosbox-0.74.conf
MIXER:No Sound Mode Selected.
ALSA:Can’t subscribe to MIDI port (65:0) nor (17:0)
MIDI:Opened device:none
I started the ipx server and mounted the drive in DOSBox
Z:\>ipxnet startserver 19900
IPX Tunneling utility for DosBox
IPX Tunneling Server started
Z:\>mount c ~/dos-games
Drive C is mounted as local directory /home/pi/dos-games/
I found ipxbox on Github which says:
ipxbox is a standalone DOSBox IPX server written in Go. DOSBox clients can connect to the server and play together.
A unique feature is that it is optionally able to bridge to real
physical networks, in a manner similar to a VPN. DOSBox clients can
communicate with each other on the server, but with this feature
enabled they can also communicate with physical IPX nodes on the
connected network. So emulated DOS clients should be able to play
games against real DOS machines connected to the same network.
So, I installed Go:
pi#raspberrypi:~ $ sudo apt-get install libpcap-dev
pi#raspberrypi:~ $ export GOPATH=/home/pi/work
pi#raspberrypi:~ $ export PATH=$PATH:$GOPATH/bin
pi#raspberrypi:~ $ sudo apt-get install golang
Then I attempted to install ipxbox:
pi#raspberrypi:~ $ go get github.com/fragglet/ipxbox
pi#raspberrypi:~ $ cd work
pi#raspberrypi:~ $ go build ipxbox.go
This is the message that I get when I run this command:
#github.com/google/gopacket/pcap
go/src/github.com/google/gopacket/pcap/pcap_unix.go:34:18: fatal error: pcap.h: No such file or directory
#include <pcap.h>
compilation terminated.
Perhaps this is obvious, but I'm not very familiar with Linux. Does anyone have any suggestions for what is causing this?
You need to install the pcap development packages.
sudo apt-get install libpcap-dev

Ejecting/unmounting random USB flash drive in Raspberry pi / Python

So I'm trying to get a working code in Python that will eject/unmount all USB flash drives attached to the Pi (Running Raspbian) - so that they can be removed safely. The final code will be run from within the python program.
Additionally, I'd like to eject/unmount the USB flash drive even if it's in use.
I've looked around and can't see how to do this. Thanks.
udisks --detach /media/pi/DOCS/ - 'Blocked device... Resource temporarily available'...
udisks --detach /media/pi/ - 'Blocked device...Resource temporarily available'...
udisks --detach /media/ - 'Blocked device...Resource temporarily available'...
sudo udisks --detach /media/pi/DOCS/ - still blocked...
sudo umount /path/to/devicename - command not found...
eject /media/pi/DOCS/ - Unable to open '/dev/sda'
(DOCS is the name if my USB flash drive. - though I want to eject all USB flash drives - not just my one)
So I'm going to ask the user in Python to select their USB flash drive from a list, which is pretty easy (just read in the folder) - so I will have the pathway to the USB. I'm still not sure which code can safely disconnect the USB flash drive - Maybe more research is the answer. Thanks for your help so far.
For udisks --detach the parameter should be the device, not the mounting point.
For example, if the USB Disk is /dev/sdb the command would be udisks --detach /dev/sdb
If the command still doesn't work you could try udiskctl power-off -b <device> which should also work.
so I found the answer:
sudo eject /dev/sda1
-This disconnects the USB flash drive on a Raspberry Pi.
Thank you very much to everyone who helped!

Ubuntu 16 upgrade results incredibly slow wifi

I recently upgraded to Ubuntu16 from 14. Everything went fine, however my wifi connection went to a crawl. I actually experienced this on a previous system that I installed Ubuntu16 on and because of that, stuck with Ubuntu14 for as long as I could until version lag forced me to upgrade.
I came across this solution that was referring to Ubuntu 17
https://askubuntu.com/questions/905288/extremely-slow-connection-after-17-04-update
And it seemed to do the trick!
The only issue is that now after a system suspend or boot-up, I have to run
sudo systemctl restart systemd-resolved
Otherwise I cannot connect to any server.
Its not a huge deal, I've aliased it at this point, but it would be nice get it operating appropriately.
Thanks for the help!
Download this link. If the download by the first link failed, download this file.
Open the Terminal and run these commands on your ubuntu pc.
cd rtlwifi_new-master
make
sudo make install
sudo modprobe -rv rtl8723be
sudo modprobe -v rtl8723be ant_sel=2
sudo ip link set wlp13s0 up
sudo iw dev wlp13s0 scan

Resources