I used my computer to connect to the beaglebone blue's network, how to use bbb assign a static ip for my computer

I found out the pins for DC motor m1
in1 = GPIO2.0 T13 / in2 = GPIO0.31 U17 / PWM EHRPWM1A U14

example config-pin -a P9_41 out
config-pin -q P9_41

so what is GPIO2.0 T13 and GPIO0.31 and PWM EHRPWM1A U14

Migrated from jadonk#53
Originally created by @ansarid on Tue, 30 Jul 2019 17:03:45 GMT

Currently we have a large robot that is using the GPS UART-RX and UART-TX as PWM outputs for an H-Bridge that only allows a PWM logic level of 5.5v max (this is why we are not using the on board motor outputs). During boot our PWM pins get pulled high which is an issue because it causes the robot to start moving.

Is there a way to configure pins to stay low on boot to avoid this issue?

Migrated from jadonk#33
Originally created by @jadonk on Wed, 12 Oct 2016 21:34:23 GMT

I have not found a document that tells us which pin on the motor driver schematic corresponds to pins 1 or 0 of each motor driver. Where can we find this?

For example. Is motor 1 pin 1 located on the lower or upper pin in this photo?

I am not sure whether I am allowed to ask this question here, but any help is pretty much appreciated. I tried to change the wifi config.
connmanctl> tether wifi disable ...
But no effect . What can I do?

• currently running/booting Debian 9.2 2017-10-10 4GB SD IoT from sd card
• already pluged in 12Vdc adapter to improve power-same result
• tried to shutdown -r now
• and replaced the image on sd card with this one: Debian 9.1 2017-09-21 4GB SD IoT image

Hope someone can help. :(

Migrated from jadonk#42
Originally created by @jadonk on Mon, 30 Jan 2017 06:32:48 GMT

Commits 4e067f5 and f9327df corrupted the XML file. I plan to convert the XML file to CSV and request that @StrawsonDesign re-applies the changes and have @erikwelsh assist in confirming the document against the design.

I'm definitely a newby but it looks like there are some errors on this spreadsheet. I would like to edit it, but only if someone would review my work. I am thinking about marking each cell I edited with a colored background to make it easy to see my changes. How should I submit my suggested changes?

Migrated from jadonk#28
Originally created by @jadonk on Wed, 12 Oct 2016 20:37:33 GMT

This would be to assist in new users locating specific connectors.

May I run a BB-BLACK REVc program on a BB-BLACK WIFI straightly ???

Migrated from jadonk#54
Originally created by @dorovl on Tue, 10 Dec 2019 11:04:05 GMT

According to the datasheet of the TB6612FNG circuit have an output current: IOUT = 1.2 A(ave)/3.2 A (peak) but also a built-in thermal shutdown circuit. I first measured the running (0.2 A) and starting current (1.2 A) of my motors and then connected them to the board.

I tested the motors with "rc_test_motors" program from Robot Control Library and this worked fine. Meanwhile, I also added the "-s {duty}" argument which sweeps motors back and forward at duty cycle. I applied for test a very short duty cycle of level 1, which induced a very high current and the burned-out the driver IC.

In a pernicious way, after the incident, the drivers IC are sinking a very high current (dissipating a lot of heat) which caused a malfunction of the eMMC (read only file system). To continue to operate my BeagleBone, it was necessary to undersold the driver ICs with hot air. However, the conformal coating material was infiltrated between the circuit and the PCB making undersoldering impossible without raising the air hot temperature over 400 °C. This damaged the plastic connectors nearby, but my BeagleBone is still working.

• We recommend to use a fast current limiter because it seems that the built-in thermal shutdown circuit has in not fast enough for transient effects over-current protection.

I'm trying to use /dev/ttyS0 (/dev/ttyO0) connected to a half-duplex bus. For the presumed reason that the serial debug console is attached to /dev/ttyS0` I cannot boot the BBBlue when the device is plugged in.

How can I disable the debug serial console? I could not find where all kernel parameters are defined. I was able to add some parameters by fiddling with /boot/uEnv.txt but could not remove the default parameters and dmesg shows me Kernel command line: console=ttyO0,115200n8 ....

Thanks,
Gaël

I have my BeagleBone blue connected to my laptop using the micro usb and it doesn't light any led. I have been working with it for a while without problems. I don't know if i can do anything or if is dead

https://github.com/beagleboard/beaglebone-blue/wiki/One-Liner-Module-Tests

Migrated from jadonk#52
Originally created by @GDV0 on Sun, 07 Jul 2019 12:47:45 GMT

Hello,

Working with a Beaglebone Blue rev A2, I have measured 5V on UART and EQEP encoder connectors, which is not consistent with the 3V3 defined in the schematic.

It's been a while since I fired up my Blue, but I just installed Debian 10.0 2019-07-07 4GB SD IoT. After booting, I noticed there are no battery lights. Apparently the ADC isn't being loaded by default. There is nothing in /sys/bus/iio/devices/.

root@beaglebone:/# rc_battery_monitor 
WARNING: instance of rc_battery_monitor already running
Killing it and starting a new instance
ERROR in rc_adc_init, failed to open iio adc interface
: No such file or directory
Perhaps kernel or device tree is too old

root@beaglebone:/# /opt/scripts/tools/version.sh
git:/opt/scripts/:[46d33928c4a396ef472829bcf22761546e550a6f]
eeprom:[A335BNLTBLA21703EMBL0014]
model:[TI_AM335x_BeagleBone_Blue]
dogtag:[BeagleBoard.org Debian Image 2019-07-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-gb96b20de74]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.03-rc2-00002-g11d4fd]:[location: dd MBR]
kernel:[4.19.50-ti-r20]
nodejs:[v10.15.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.4.20190610.0-0rcnee0~buster+20190610]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~buster+20190227]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327]
pkg:[firmware-ti-connectivity]:[20190114-1]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 cape_universal=enable quiet]
dmesg | grep remote
[    1.379128] remoteproc remoteproc0: wkup_m3 is available
[    1.540959] remoteproc remoteproc0: powering up wkup_m3
[    1.541085] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[    1.544472] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[    1.102508] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

Migrated from jadonk#20
Originally created by @jadonk on Tue, 26 Jul 2016 18:22:45 GMT

Reduce number of characters

Expected Behavior

Plugging in USB or 12V barrel jack power supply to BeagleBone Blue (BBBL) should

1. Enable the user LEDs;
2. Turn the "ON" LED on;
3. Be recognizable by Windows (if plugged in by USB).

Actual Behavior

Using the USB or 12V barrel jack power supply has the following characteristics:

• Momentarily flashes once the "ON" LED;
• All other LEDs are off for the entire duration;
• When specifically the USB is plugged in:
  • No USB is detected by Windows.;
  • SSH at 192.168.7.2 fails;
  • Pinging 192.168.7.2 fails.
• When specifically the 12V barrel jack is plugged in:
  • The "CHG" LED glows for the entire duration.

This issue began when the 12V/2A barrel jack power supply was plugged into a powered off BBBL. At that time, the BBBL LEDs glowed as usual, and immediately afterwards, turned off (excluding the "CHG" LED).

Note: The barrel jack power supply was previously used with no concerns.

Attempted Solutions

• Holding down the SD (boot select) button while powering on (either by inserting USB, barrel jack, or by pressing the POW (power) button) when a bootable microSD card is present.
• Holding down the POW button.
• Holding down both SD and POW button at the same time or one after another and other button pressing configurations.
• Pressing the RST button.
• Reflashing the SD card with the latest image (note that the eMMC already had the latest image) and then inserting it into to the BBBL

Pressing the POW button momentarily flashes the "ON" LED once.

Using a multimeter, 5V was detected across the GPS port (pins identified from the PINOUT section of this wiki) suggesting that the whole circuitry may not be dead.

Specifications

* Originally was used when the problem first occurred; This image was previously used with no concerns.

Note: This issue maybe a duplicate of this older post which was unanswered.

my device is beaglebone blue. I refer to the https://github.com/MarkAYoder/PRUCookbook/tree/master/docs/04debug/code
when i When I execute this script :uart_setup.sh
export PRUN=0
export TARGET=uart1
echo PRUN=$PRUN
echo TARGET=$TARGET

Configure tx

config-pin P9_24 pru_uart

Configure rx

config-pin P9_26 pru_uart

then it will report error:
x$ config-pin P9.24 pru_uart
dash: echo: I/O error
Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P9_24_pinmux/state
debian@beaglebone:/sys/devices/platform/ocp/ocp:P9_24_pinmux

Doesn't it need to be configured of the BBBLUE?

Migrated from jadonk#17
Originally created by @jadonk on Wed, 29 Jun 2016 20:25:16 GMT

More of a question, not an issue. What is the amperage consumption on the BeagleBone Blue when running from a 2s Lipo?

The connector that plugs inside is not retained. By vibrations, this connector comes out and this is particularly dangerous in the context of a flight controller (our project).

• Therefore we recommend to put also a white JST-SH connectors on the next version.

Should anything be done about thermal management for the CPU? I don't see this issue addressed anywhere in the BBBlue discussion.

What is the intended purpose of temperature reading on the MPU9250? Is it appropriate to measure ambient temperature or is it close to heat-generating components on the blue?

According to the datasheet of the TB6612FNG circuit have an output current: IOUT = 1.2 A(ave)/3.2 A (peak) but also a built-in thermal shutdown circuit. I first measured the running (0.2 A) and starting current (1.2 A) of my motors and then connected them to the board.

I tested the motors with "rc_test_motors" program from Robot Control Library and this worked fine. Meanwhile, I also added the "-s {duty}" argument which sweeps motors back and forward at duty cycle. I applied for test a very short duty cycle of level 1, which induced a very high current and the burned-out the driver IC.

In a pernicious way, after the incident, the drivers IC are sinking a very high current (dissipating a lot of heat) which caused a malfunction of the eMMC (read only file system). To continue to operate my BeagleBone, it was necessary to undersold the driver ICs with hot air. However, the conformal coating material was infiltrated between the circuit and the PCB making undersoldering impossible without raising the air hot temperature over 400 °C. This damaged the plastic connectors nearby, but my BeagleBone is still working.

• We recommend to use a fast current limiter because it seems that the built-in thermal shutdown circuit has in not fast enough for transient effects over-current protection.

On many occasions my students powered up their device and failed to see a wifi signal. NEITHER THE PROBLEM NOR MY SOLUTIONS CAN BE CONSISTENTLY REPEATED, but it has recurred over several months with 10-20 different units with different images flashed, so I need help. I gave the following instructions to make sure wifi is running:

1. Be sure to power with a 12v source at barrell plug instead of USB, which may be insufficient to run wifi at times. (is this true???) - this sometimes resolved the problem.
2. Shut down your blue, remove power, remove SD card and replace SD card. Boot back up and check for wifi functionality. - this sometimes resolved the problem.

Hi

It is possible with this version beaglebone-blue to control motor stepper driver like leadshine dm556 ?

Also for this use, machinekit can work with this board ?

Best regards.

1. What exact steps tell my blue to boot from microSD?
2. What steps tell my blue to boot from onboard memory?
3. How can I query my blue on where it has booted from?
4. Can I tell by the LEDs where the blue is running it's OS?

BeagleBone_Blue_sch.pdf shows "TB6621FNG" but should be "TB6612FNG".

Don't feel bad though, you're not the only one!
sparkfun/Motor_Driver-Dual_TB6612FNG#1

I am using DSMX satellite recv on my beaglebone blue and have a DX6 transmitter, which is binded to sat recv via DSM2 protocol running (rc_bind_dsm). After few minutes of binding , I loose DSM connection and the satellite recv starts blinking. I have no clue whats triggering it.

Any suggestions / help would be appreciated.

Thanks.

Migrated from jadonk#56
Originally created by @dorovl on Tue, 10 Dec 2019 11:10:51 GMT

We had a bad signal intensity (as we where quite far from the router). Therefore, we tried to take out the WiFi antenna to obtain a better a signal intensity. Lot of pictures like https://github.com/beagleboard/beaglebone-blue/blob/master/docs/BeagleBone_Blue_balloons.png illustrate BBBL with the antenna out. Therefore, we don't saw any constraints to rotate the antenna.

To rotate the antenna there are two options:

1. Rotate the antenna without extracting it; the risk is to exert an asymmetrical tearing on the whole assembly when passing over the WiFi chip,
2. Extract the antenna from the receptacle, rotate the antenna 180° and push back the antenna on the receptacle.

Option 1 works quite well (tested by me, but not sure that it does not cause exfoliation of the printed circuit board). Option 2 causes the tearing of the receptacle (what happened to my father) because the anchoring of the receptacle on the printed circuit board is only superficial. Therefore, the required extraction force is bigger than the force that the attachment can support. Please note that we applied the instructions of the Hirose Electric connector manufacturer, consisting to to pull off vertically the U.FL Cable Assembly, in the direction of the connector mating axis (we don't used the extraction tool but but some plastic tweezers):

• We recommend that on the next version, the anchoring of the receptacle on the printed circuit board must be stronger (attached to a anchorage pin inserted in the PCB); some extraction test should be made on the first prototypes.
• For the meantime, a warning notice should be present with the product.

Hello, I am an electronics enthusiast, I start with a beaglebone-blue . I would like to run two DC motors with a NodeMCU motor shield, but I can't connect my beaglebone to the shield. I can't find the right GPIO to connect the two.

Looks like the docx version was updated without converting to pdf as well.

Migrated from jadonk#30
Originally created by @jadonk on Wed, 12 Oct 2016 21:08:39 GMT

Migrated from jadonk#41
Originally created by @mirkix on Fri, 23 Dec 2016 22:10:42 GMT

Hi, is it an option to connect the MPU 9250 via SPI and not via I2C? With Ardupilot we can sample at 4 kHz / 8 kHz (acc gyro) in this case I2C is not fast enough for the data transfer. It is possible to sample slower too, than the transfer speed via I2C should be okay.

It would be convenient if the "BeagleBone_Blue_ShortSpec.pdf" and the website could mention the specs of the motor drivers, i.e., 1.2A continuous, 3.2A peak, 2.5-13.5V; and/or the part number TB6612FNG. Thank-you.

Hi,

I just bought a beaglebone blue, plugged it in and share my internet connection from the computer using /sbin/route add default gw 192.168.7.1 and changing the adapter settings to automatic ip configuration (beagle) and share in the ethernet adapter.

After that I was able to ping 8.8.8.8 and www.google.com. However, when I attempted to apt-get update install it gave me an error saying "Failed to connect to deb.nodesource.com port 443: Connection refused".

I continued testing it and when I attempted to git clone some library, I was given the same "Failed to connect" on that same port.

I shut down the windows firewall and my antivirus and even made some rules for the firewall to allow connections in/out to port 443 and nothing.

I tried to check whether the system was listening on port 443 and this is what I got,

root@beaglebone:/var/lib/cloud9# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 5700/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 4436/sshd
tcp6 0 0 :::8080 :::* LISTEN 1323/apache2
tcp6 0 0 :::80 :::* LISTEN 1/init
tcp6 0 0 :::53 :::* LISTEN 5700/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 4436/sshd
tcp6 0 0 :::3000 :::* LISTEN 1/init
tcp6 0 0 :::1880 :::* LISTEN 1/init

Pleasee help. I don't know how to solve this and I am sure I am not the only one.

Regards,
Oscar

Migrated from jadonk#9
Originally created by @jadonk on Thu, 03 Dec 2015 22:16:52 GMT

Migrated from jadonk#38
Originally created by @jadonk on Mon, 07 Nov 2016 19:18:32 GMT

Migrated from jadonk#39
Originally created by @jadonk on Tue, 15 Nov 2016 20:39:05 GMT

http://www.ti.com/tool/TIDA-00982#Technical Documents

Migrated from jadonk#51
Originally created by @shreks7 on Sun, 08 Apr 2018 19:33:01 GMT

It is impossible to use the BBBlue, it always goes into read-only mode whenever there is a write attempt to eMMC or the SD card (32gb).
It also gives Input/Output error after it goes the read-only file system mode.

It's a very irritating bug, any fixes? or Is it a hardware issue?

Migrated from jadonk#46
Originally created by @adanmaa on Wed, 26 Apr 2017 23:39:56 GMT

Had this board for a day. Powered it on and opened the getting started page. RNDIS tethering doesn't work on OS X Yosemite. Serial connection doesn't work unless you download full drivers from FTDI. I tried accessing beagle bone access point but don't know the password. Was able to login through the terminal with default password, but don't know how to update software without network connection. Now beagle bone doesn't seem to be working - not able to browse device files in Finder window; won't connect serially; can't see access point; and RNDIS won't work. Any other way to access beagle bone?

Hi,
I am wondering how to use the pin GPIO1_25 for Beaglebone Blue?
I can't find any information in the pin head sheet, although it exists in the schematics.

Thx!

We had a bad signal intensity (as we where quite far from the router). Therefore, we tried to take out the WiFi antenna to obtain a better a signal intensity. Lot of pictures like https://github.com/beagleboard/beaglebone-blue/blob/master/docs/BeagleBone_Blue_balloons.png illustrate BBBL with the antenna out. Therefore, we don't saw any constraints to rotate the antenna.

To rotate the antenna there are two options:

1. Rotate the antenna without extracting it; the risk is to exert an asymmetrical tearing on the whole assembly when passing over the WiFi chip,
2. Extract the antenna from the receptacle, rotate the antenna 180° and push back the antenna on the receptacle.

Option 1 works quite well (tested by me, but not sure that it does not cause exfoliation of the printed circuit board). Option 2 causes the tearing of the receptacle (what happened to my father) because the anchoring of the receptacle on the printed circuit board is only superficial. Therefore, the required extraction force is bigger than the force that the attachment can support. Please note that we applied the instructions of the Hirose Electric connector manufacturer, consisting to to pull off vertically the U.FL Cable Assembly, in the direction of the connector mating axis (we don't used the extraction tool but but some plastic tweezers):

• Therefore we recommend that on the next version, the anchoring of the receptacle on the printed circuit board must be stronger (attached to a anchorage pin inserted in the PCB); some extraction test should be made on the first prototypes.
• For the meantime, a warning notice should be present with the product.

Migrated from jadonk#48
Originally created by @jadonk on Tue, 16 May 2017 15:21:22 GMT

Battery should not drain when device is powered down.

Migrated from jadonk#55
Originally created by @dorovl on Tue, 10 Dec 2019 11:08:59 GMT

The connector that plugs inside is not retained. By vibrations, this connector comes out and this is particularly dangerous in the context of a flight controller (our project).

Please note I'm referring to the "Power out" and "4 ADC" connectors (see red arrow):

• We recommend to put also a white JST-SH connectors on the next version.

In BOM and schematic files, L1 and L2 are both 6.8uH but the used component is 6.3uH (Taiyo Yuden NRS6045T6R3MMG). I assume wrong part number is written (NRS6045T6R3MMG).

is there already a BLUE version analog to the
'Beaglebone Black System Reference Manual'

Can anyone suggest where to find gpiochip and pin numbers to be able to use it with the libgpiod library?

How can i plug 3dr telemetry via usb cable?