Nimbelink cape lite for beaglebone issue



I’ve got a nimbelink beaglebone cape lite (with a nimbelink NL-SW-LTE-S7648 cell module) plugged into a
beaglebone green. Nothing else is connected. I SSH into the beaglebone and try to communicate with the
module using AT cmds via minicom but no response. I had this working 6 months ago but with a different module - NL-SW-GPRS.
I accidently damaged the module so I decided to switch the more recent NL-SW-LTE-S7648.

I checked to see if the device tree overlay was loaded (dmesg | grep NL-AB-BBCL) but I’m not sure if actually
is. The message I get is different than the cape lite manual shows. I get -

[0.00]Kernel command line: console=ttyO0, 115200n8 bone_capemgr.uboot_capemgr_enabled=1 root/dev/mmcblk0p1 ro
rootfstype=ext4 rootwait uboot_detected_capes=NL-AB-BBCL, coherent_pool=1M net.ifnames=0 quiet

I re-install the overlays =>
sudo apt update
sudo apt install bb-cape-overlays

Nothing changes.

UART4 is enabled in the uEnv.txt.

Any help will be greatly appreciated.

thanks toyo


@toyose, that’s showing it loaded properly…

On these newer modem’s the usb interface is enabled, have you tried connecting a usb cable from the cape to the board? you should see a new usb interface show up.



hi Robert

Thanks for your reply.
I tried that as well. Connecting the usb through beaglebone did not work.
Connecting directly windows, Ubuntu or debian did not detect the USB.
It looks as if the cell module is damaged I dont know anyway to determine this?


@toyose, thru the uart, does the device respond to AT commands, such as:

AT+KGPIO=10,1 //Turn on D1 LED
AT+KGPIO=10,0 //Turn off D1 LED



The cape is set up to communicate via uart4. So I ssh into beaglebone and configure
uart4 to 115200, 8, 1, no flow control.
I never actually tried using usb before until you mentioned it.

So to answer your question, I’m not even getting the simple AT cmd to work. No led indication
of the status of the module, no power led. I dont even know how to begin to
troubleshoot it.



Just got a working cape/modem in the lab this morning, can you dump the configuration of your beagle:

debian@beaglebone:~$ sudo /opt/scripts/tools/ 
dogtag:[ Debian Image 2018-11-25]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-gd5b4c4b656]:[location: dd MBR]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=NL-AB-BBCL, coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[    1.110666] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[    1.122504] gpio-of-helper ocp:cape-universal: ready

How are you powering the device? Are you using the recommended 12V DC connector?
The modem i have here needs 921600, it’s responding to basic commands:

debian@beaglebone:~$ tio -b 921600 /dev/ttyO4
[tio 18:37:53] tio v1.26
[tio 18:37:53] Press ctrl-t q to quit
[tio 18:37:53] Connected

+CESQ: 99,99,255,255,255,255




tio @ 921600 still did not work.
My power supply is a 12v 2A XP Power adapter powered from the cape.