UART connection with 4G Module.

Hi, I was initally struggling to get my 4g module up and running with BBB but now I have managed to get it running when connected via a FTDI breakout board and when connected via USB directly.

Now, I am trying to connect my BBB to the module using UART.

config-pin p9.24 uart
config-pin p9.26 uart

after this,
I have written a python code using pyserial to open ttyS1 and send AT commands and observe the output but it is not giving any outputs.

I wanted to make sure if everything was alright so I ran dmesg | grep tty
this returned the following,

debian@BeagleBone:~$ dmesg | grep tty
[    0.000000] Kernel command line: console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
[    8.422035] printk: console [ttyS0] disabled
[    8.422151] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 20, base_baud = 3000000) is a 8250
[    8.450549] printk: console [ttyS0] enabled
[    8.452561] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 27, base_baud = 3000000) is a 8250
[    8.454253] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 28, base_baud = 3000000) is a 8250
[    8.456137] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 43, base_baud = 3000000) is a 8250
[    8.457479] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 44, base_baud = 3000000) is a 8250
[    8.459088] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 45, base_baud = 3000000) is a 8250
[   22.432314] systemd[1]: Unnecessary job for /sys/devices/platform/ocp/44c00000.interconnect/44c00000.interconnect:segment@200000/44e09050.target-module/44e09000.serial/tty/ttyS0 was removed.
[   22.444221] systemd[1]: Created slice system-getty.slice.
[   22.451844] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  130.622344] usb 1-1: cp210x converter now attached to ttyUSB0
**[ 8379.531448] omap8250 48022000.serial: ttyS1 (1): invalid RTS setting, using RTS_ON_SEND instead**
[ 8717.299715] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

I dont understanding what does the [ 8379.531448] omap8250 48022000.serial: ttyS1 (1): invalid RTS setting, using RTS_ON_SEND instead mean ? I think that might be the key to solving my problem.
can someone help me out with this? where am I going wrong ?
thanks.

I saw your conversation with melta101, so I couldn’t resist trying it out.

If I bridge P9.24 and P9.26 and run minicom -D/dev/ttyS1 -b115200, it just works.
I am running an older build mind you (Linux beaglebone 4.19.94-ti-r74).
The newer builds don’t use config-pin anymore, but use the device-tree to control the pinmux.

Could that be it, I wonder?

config-pin works fine for me,
my build is Linux BeagleBone 5.10.168-ti-r71

What is the exact name of the image you’re running?

Never tried the 5.10.x kernel, but I’m willing to give it a go, just for kicks.

cat /etc/dogtag
returned
BeagleBoard.org Debian Bullseye IoT Image 2023-09-02

Please include the output of

sudo beagle-version

Regards,

Using the image you’re using @ab25, I am able to reproduce your issue.

Can’t push anything through ttyS1 on this image at all, when using the exact same
method that works without fail on the 4.94 Buster image.

So I sincerely doubt there’s anything wrong with your hardware.

eeprom:[A335BNLT00C02238SBB05029]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Bullseye IoT Image 2023-09-02]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2022.04-ge0d31da5 (Aug 04 2023 - 18:48:26 +0000)]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[BB-ADC-00A0.kernel]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.kernel]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0.kernel]
kernel:[5.10.168-ti-r71]
nodejs:[v12.22.12]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
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.14.20210821.0-0~bullseye+20210821]
pkg:[bb-customizations]:[1.20230720.1-0~bullseye+20230720]
pkg:[bb-usb-gadgets]:[1.20230414.0-0~bullseye+20230414]
pkg:[bb-wl18xx-firmware]:[1.20230414.0-0~bullseye+20230414]
pkg:[kmod]:[28-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20210315-3]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input render bluetooth netdev i2c gpio admin tisdk weston-launch cloud9ide]
cmdline:[console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[    8.854181] remoteproc remoteproc0: wkup_m3 is available
[   40.150556] remoteproc remoteproc0: powering up wkup_m3
[   40.150776] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[   40.151073] remoteproc remoteproc0: remote processor wkup_m3 is now up
[   58.799283] remoteproc remoteproc1: 4a334000.pru is available
[   58.814923] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
[   58.799283] remoteproc remoteproc1: 4a334000.pru is available
[   58.814923] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pinctrl-single
[    8.393850] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[    8.395422] gpio-of-helper ocp:cape-universal: Failed to get gpio property of 'P8_03'
[    8.395453] gpio-of-helper ocp:cape-universal: Failed to create gpio entry
[    9.057298] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0 name='P8_03'
[    9.057510] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1 name='P8_04'
[    9.057672] gpio-of-helper ocp:cape-universal: Allocated GPIO id=2 name='P8_05'
[    9.057852] gpio-of-helper ocp:cape-universal: Allocated GPIO id=3 name='P8_06'
[    9.058286] gpio-of-helper ocp:cape-universal: Allocated GPIO id=4 name='P8_07'
[    9.058494] gpio-of-helper ocp:cape-universal: Allocated GPIO id=5 name='P8_08'
[    9.058806] gpio-of-helper ocp:cape-universal: Allocated GPIO id=6 name='P8_09'
[    9.058980] gpio-of-helper ocp:cape-universal: Allocated GPIO id=7 name='P8_10'
[    9.059164] gpio-of-helper ocp:cape-universal: Allocated GPIO id=8 name='P8_11'
[    9.059372] gpio-of-helper ocp:cape-universal: Allocated GPIO id=9 name='P8_12'
[    9.059630] gpio-of-helper ocp:cape-universal: Allocated GPIO id=10 name='P8_13'
[    9.059808] gpio-of-helper ocp:cape-universal: Allocated GPIO id=11 name='P8_14'
[    9.059985] gpio-of-helper ocp:cape-universal: Allocated GPIO id=12 name='P8_15'
[    9.060156] gpio-of-helper ocp:cape-universal: Allocated GPIO id=13 name='P8_16'
[    9.060333] gpio-of-helper ocp:cape-universal: Allocated GPIO id=14 name='P8_17'
[    9.060496] gpio-of-helper ocp:cape-universal: Allocated GPIO id=15 name='P8_18'
[    9.060667] gpio-of-helper ocp:cape-universal: Allocated GPIO id=16 name='P8_19'
[    9.060827] gpio-of-helper ocp:cape-universal: Allocated GPIO id=17 name='P8_20'
[    9.061014] gpio-of-helper ocp:cape-universal: Allocated GPIO id=18 name='P8_21'
[    9.061183] gpio-of-helper ocp:cape-universal: Allocated GPIO id=19 name='P8_22'
[    9.061341] gpio-of-helper ocp:cape-universal: Allocated GPIO id=20 name='P8_23'
[    9.061550] gpio-of-helper ocp:cape-universal: Allocated GPIO id=21 name='P8_24'
[    9.061719] gpio-of-helper ocp:cape-universal: Allocated GPIO id=22 name='P8_25'
[    9.061895] gpio-of-helper ocp:cape-universal: Allocated GPIO id=23 name='P8_26'
[    9.062072] gpio-of-helper ocp:cape-universal: Allocated GPIO id=24 name='P8_27'
[    9.062233] gpio-of-helper ocp:cape-universal: Allocated GPIO id=25 name='P8_28'
[    9.062407] gpio-of-helper ocp:cape-universal: Allocated GPIO id=26 name='P8_29'
[    9.062673] gpio-of-helper ocp:cape-universal: Allocated GPIO id=27 name='P8_30'
[    9.062857] gpio-of-helper ocp:cape-universal: Allocated GPIO id=28 name='P8_31'
[    9.063034] gpio-of-helper ocp:cape-universal: Allocated GPIO id=29 name='P8_32'
[    9.063204] gpio-of-helper ocp:cape-universal: Allocated GPIO id=30 name='P8_33'
[    9.063385] gpio-of-helper ocp:cape-universal: Allocated GPIO id=31 name='P8_34'
[    9.063582] gpio-of-helper ocp:cape-universal: Allocated GPIO id=32 name='P8_35'
[    9.063748] gpio-of-helper ocp:cape-universal: Allocated GPIO id=33 name='P8_36'
[    9.063921] gpio-of-helper ocp:cape-universal: Allocated GPIO id=34 name='P8_37'
[    9.064083] gpio-of-helper ocp:cape-universal: Allocated GPIO id=35 name='P8_38'
[    9.064272] gpio-of-helper ocp:cape-universal: Allocated GPIO id=36 name='P8_39'
[    9.064450] gpio-of-helper ocp:cape-universal: Allocated GPIO id=37 name='P8_40'
[    9.064622] gpio-of-helper ocp:cape-universal: Allocated GPIO id=38 name='P8_41'
[    9.064792] gpio-of-helper ocp:cape-universal: Allocated GPIO id=39 name='P8_42'
[    9.064949] gpio-of-helper ocp:cape-universal: Allocated GPIO id=40 name='P8_43'
[    9.065121] gpio-of-helper ocp:cape-universal: Allocated GPIO id=41 name='P8_44'
[    9.065311] gpio-of-helper ocp:cape-universal: Allocated GPIO id=42 name='P8_45'
[    9.065475] gpio-of-helper ocp:cape-universal: Allocated GPIO id=43 name='P8_46'
[    9.065650] gpio-of-helper ocp:cape-universal: Allocated GPIO id=44 name='P9_11'
[    9.065837] gpio-of-helper ocp:cape-universal: Allocated GPIO id=45 name='P9_12'
[    9.066022] gpio-of-helper ocp:cape-universal: Allocated GPIO id=46 name='P9_13'
[    9.066194] gpio-of-helper ocp:cape-universal: Allocated GPIO id=47 name='P9_14'
[    9.066353] gpio-of-helper ocp:cape-universal: Allocated GPIO id=48 name='P9_15'
[    9.066526] gpio-of-helper ocp:cape-universal: Allocated GPIO id=49 name='P9_16'
[    9.066789] gpio-of-helper ocp:cape-universal: Allocated GPIO id=50 name='P9_17'
[    9.066963] gpio-of-helper ocp:cape-universal: Allocated GPIO id=51 name='P9_18'
[    9.067132] gpio-of-helper ocp:cape-universal: Allocated GPIO id=52 name='P9_19'
[    9.067332] gpio-of-helper ocp:cape-universal: Allocated GPIO id=53 name='P9_20'
[    9.067535] gpio-of-helper ocp:cape-universal: Allocated GPIO id=54 name='P9_21'
[    9.067708] gpio-of-helper ocp:cape-universal: Allocated GPIO id=55 name='P9_22'
[    9.067873] gpio-of-helper ocp:cape-universal: Allocated GPIO id=56 name='P9_23'
[    9.068048] gpio-of-helper ocp:cape-universal: Allocated GPIO id=57 name='P9_24'
[    9.068508] gpio-of-helper ocp:cape-universal: Allocated GPIO id=58 name='P9_25'
[    9.068708] gpio-of-helper ocp:cape-universal: Allocated GPIO id=59 name='P9_26'
[    9.068889] gpio-of-helper ocp:cape-universal: Allocated GPIO id=60 name='P9_27'
[    9.069053] gpio-of-helper ocp:cape-universal: Allocated GPIO id=61 name='P9_28'
[    9.069235] gpio-of-helper ocp:cape-universal: Allocated GPIO id=62 name='P9_29'
[    9.069406] gpio-of-helper ocp:cape-universal: Allocated GPIO id=63 name='P9_30'
[    9.069600] gpio-of-helper ocp:cape-universal: Allocated GPIO id=64 name='P9_31'
[    9.069774] gpio-of-helper ocp:cape-universal: Allocated GPIO id=65 name='P9_41'
[    9.069936] gpio-of-helper ocp:cape-universal: Allocated GPIO id=66 name='P9_91'
[    9.070109] gpio-of-helper ocp:cape-universal: Allocated GPIO id=67 name='P9_42'
[    9.070265] gpio-of-helper ocp:cape-universal: Allocated GPIO id=68 name='P9_92'
[    9.070276] gpio-of-helper ocp:cape-universal: ready
dmesg | grep wlcore
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

damn!
so thats the issue with kernel itself…
Can we raise this issue elsewhere so they can patch it up?

You already have by posting about it here.

I haven’t been following the BBB development recently,
so I don’t know exactly how far they’ve gotten with the 6.1.x kernel.

Might be worth checking out, just be aware of the eMMC issue.
Or you might unblock yourself by stepping back to Buster if that’s possible.

I am having a similar issue with the 6.1.83-ti-r35 kernel running Bookworm. More information is available at: https://discord.com/channels/1108795636956024986/1117126674832695316/1276648423457820724

Any insight would be appreciated.

I have finally solved this issue. But, I do not fully understand. Anyway it turns out the that UART4 will be enabled if I use: uboot_overlay_addr4=BB-UART4-00A0.dtbo Previously I had a custom DT file on addr0 and UART4 on addr1. I am not sure why this works going to addr4. On kernel 5.10.168-ti-r79 the custom DT file is on addr0 and UART4 is on addr1 and is working as expected.

Hi, Do

I have 5.10.168-tir71 and I couldn’t even get a normal loopback running.
I wonder why ?

Try cat /proc/interrupts and see if the dmesg information matches up. I cannot imagine that it won’t. Otherwise, I have no suggestions.