Awesome - thank you!

These are my two original boxes - one for Bittle and one for the first Bittle X.

I ended up using Windows. Even after installing the Mac driver I could never get it work.

This was from the command line version installed independently- but the i integrated version gets the same error. Same setup (standalone version works on windows). I installed the serial part driver on mac same result. It does talk to the board as it can find most of the board details - but always gets this failed to upload stub error. It even gets it for the passive commands like 'esptool flash_id' I tried it with the partition scheme in your screenshot and got the same result.

I work for GitLab and I want to create demos of CI/CD build and deploy. I already have the shell runner working here: https://stat.dog and then part of the new SDV vehicle architecture here: https://sdv.bot.

Here is the output of gpio readall It is much more readable when the display area is wider. gpio readall +------+-----+----------+--------+---+ ZERO2W +---+--------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+--------+---+----++----+---+--------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 264 | 0 | SDA.1 | OFF | 0 | 3 || 4 | | | 5V | | | | 263 | 1 | SCL.1 | OFF | 0 | 5 || 6 | | | GND | | | | 269 | 2 | PWM3 | OFF | 0 | 7 || 8 | 0 | ALT2 | TXD.0 | 3 | 224 | | | | GND | | | 9 || 10 | 0 | ALT2 | RXD.0 | 4 | 225 | | 226 | 5 | TXD.5 | OFF | 0 | 11 || 12 | 0 | OFF | PI01 | 6 | 257 | | 227 | 7 | RXD.5 | OFF | 0 | 13 || 14 | | | GND | | | | 261 | 8 | TXD.2 | OFF | 0 | 15 || 16 | 0 | OFF | PWM4 | 9 | 270 | | | | 3.3V | | | 17 || 18 | 0 | OFF | PH04 | 10 | 228 | | 231 | 11 | MOSI.1 | OFF | 0 | 19 || 20 | | | GND | | | | 232 | 12 | MISO.1 | OFF | 0 | 21 || 22 | 0 | OFF | RXD.2 | 13 | 262 | | 230 | 14 | SCLK.1 | OFF | 0 | 23 || 24 | 0 | OFF | CE.0 | 15 | 229 | | | | GND | | | 25 || 26 | 0 | OFF | CE.1 | 16 | 233 | | 266 | 17 | SDA.2 | OFF | 0 | 27 || 28 | 0 | OFF | SCL.2 | 18 | 265 | | 256 | 19 | PI00 | OFF | 0 | 29 || 30 | | | GND | | | | 271 | 20 | PI15 | OFF | 0 | 31 || 32 | 0 | OFF | PWM1 | 21 | 267 | | 268 | 22 | PI12 | OFF | 0 | 33 || 34 | | | GND | | | | 258 | 23 | PI02 | OFF | 0 | 35 || 36 | 0 | OFF | PC12 | 24 | 76 | | 272 | 25 | PI16 | OFF | 0 | 37 || 38 | 0 | OFF | PI04 | 26 | 260 | | | | GND | | | 39 || 40 | 0 | OFF | PI03 | 27 | 259 | +------+-----+----------+--------+---+----++----+---+--------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+--------+---+ ZERO2W +---+--------+----------+-----+------+

I think I have to: 1. enable another uart (e.g. #4), 2. set the console= line to that one ( e.g. console=serial4 ?) 3. and then configure GPIO to ensure it's GPIO is in the 5x2 GPIO block used by the Bittle to interface Can anyone validate or correct this plan?

I followed the serial configuration instructions in @rhongzhongli link and the robot does not have spasms anymore. But only when attached to the Bittle I can't ssh because it never grabs an IP address. If it is powered independently it works. I think it might have to do with the OrangePi automatically assigning uart0 to bluetooth? The only available overlay is to disable it and then there are overlays to enabled uart2-5. I also can't find a setting for console= in /boot/orangepiEnv.txt that disables serial. So far the only values I've found are "both" or "serial" Is there a way to use one of the many other uarts in the orange pi for integrating with Bittle? Here is a relevant discussion thread: https://github.com/orangepi-xunlong/orangepi-build/issues/4

@este este - Do you have an idea what parameter I would put in for height if I want it to be so close fitting that is simply does not move. I might still add back 1/16 top and bottom for very thin foam - but I'm interested in the minimum value that you might know by experience. I am thinking with the head turned sideways, rather than nose down.

Fantastic - exactly what I wa hoping for! Thanks!

Here is the latest bittle box I have and next to it a box for an old tablet that it "sort of" fits in with the head detachhed.

It is supposedly compatible - but it freezes up the robot and the Orange pi becomes unresponsive to ssh. Not sure why.

http://stat.dog - I never did get the bluetooth audio working - even in attempting to do so with recent releases. Seems like fundamental problems with the raspberry pi linux release with regard to getting bluetooth audio working reliably. It's been about 2 months since I last visited it - so maybe solved by now.

Since I was waiting on the hardware to solder I got started on getting bluetooth working before attempting GPIO - so maybe my path is due to enabling bluetooth? Do you know if the GPIO should work with the miniUART and not have to swap it to Bluetooth (assuming bluetooth is enabled) ?

One other interesting thing. Almost none of the many, many configuration changes I made to the raspberry pi requires rebooting the Nyboard (some do require rebooting the PI). If, however, the raspi-config setting for "Would you like a login shell to be accessible over serial?" is Yes or changed to yes and then changed to No - rebooting the raspberry pi is not enough - the nyboard is unresponsive until it is rebooted as well.

Ok I did a build from scratch and it would not work and had the same behavior where ardSerial would seem to delay for a very long time before failing. I exported installed packages lists and compared them for differences, /boot/config.txt, /boot/cmdline.txt. I compared raspi-configs. Finally, adding either `dtoverlay=disable-bt` or `dtoverlay=miniuart-bt` to /boot/config.txt fixes it. Since I also want a bluetooth audio connection I use the later so that just the UART switches. The weird thing - is my original build does not have `dtoverlay=miniuart-bt`, but it works. I'm wondering if I found another way to configure the UART swap while struggling to get the original working build going. Even if I did, this seems like the most self-documenting way to do this. I am going to do another build from scratch to verify I know how to go from off the shelf Raspberry Pi to working - including Bluetooth Audio.

It's working now - not exactly sure why - but that's OK because I am prepping other SD cards from scratch to learn exactly what is needed. Thanks for all your help!

@Rongzhong Li It would be great to connect on Linked In - I work in at a CI/CD company and have some ideas that would likely cause some interest in Bittle. I can't request a connection with you, but I'm at https://www.linkedin.com/in/xycd/

@Rongzhong Li Yes - as of the testing in this thread I have been ensuring this is the only connection.

I have the controller port bent backwards and use leads to connect it to the usb board when controlling it with usb so that it can be mobile even when usb connected. The controller port pins are protected by tape from shorting on the USB port edge on the Pi. The pictured configuration is how I've been trying to get the GPIO serial to work.