Beagle bone Blue Uart debug port issue

Hi All,
I am using beaglebone blue and I habe an issue using uart debug port, I always get this message " 1.734722] Kernel panic - not syncing: Fatal exception in interrupt "


when I connect the beagle board to laptop usb port, I searched for this issue and I found a solution saying that the issue is in the current so I need to connect a 2A power source but when I connect the 2A power source I am not able to get a clear message " ����wo�����w�����������w���u{{��w���}{������������뵳�����{uw�{���m��������mm"
and also I used the 12V power supply and I got same “����wo�����w�����������w���u{{��w���}{������������뵳�����{uw�{���m��������mm”

Hello @moutiry, and welcome to our little corner of the Internet.

Unfortunately the “rear-end” of the trace isn’t as informative as the beginning.
Could you grab the whole thing plus a few lines before the oops, in text form for us please?
( the scroll-bar isn’t working for me in an image, hehe )

As for the gibberish at the end, make sure your terminal is at 115200;
sometimes it helps to reset terminal after changing the line speed.

@moutiry welcome,
are you booting from emmc or sdcard ??
what OS and version ??
is there anything plugged into the bbblue other than usb-serial ??
are you connecting to a linux or windows machine (include version) ??
are you able to ssh into the bbblue @ 192.168.7.2 ??

all this helps to help you,

Welcome,
1- I am trying to boot from SD Card
2- Angstrom : Angstrom Distribution (BeagleBone, BeagleBone Black - 4GB SD) 2013-06-20 - BeagleBoard
3- no
4- Ubuntu 24.04LTS
5- yes

downloaded the image you indicated, it boots fine, no kernel panics
i’m using a 12V 2A power supply. only usb-serial adapter is attached.
have you tried a non-angstrom image ??
boot log attached,
blue-angstrom.log (4.9 KB)

if your using minicom, then start it with -C boot.log
to save ever thing to a file
to upload the file, you need to change owner to to something other than root

We need to see more of the boot log before the kernel panic. It is missing what actually caused it. Could be a corrupt SD card image, but hard to say.

1 Like

So Blue + Angstrom will be a lot of fun… The main developer for BeagleBoard who worked on Angstrom, had transferred to TI before the BeagleBone Blue was ever a dream on a schematic…

Regards,

here is the boot logs
boot.log (24.5 KB)

@moutiry
from your boot log,
U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)

from my boot log, (i.e. the image you indicated you were using)
U-Boot SPL 2017.03-rc2-00002-g11d4fd24f9 (Feb 15 2017 - 16:42:40)

my guess is that you’re booting with a u-boot from emmc
try holding the S2 button while booting, this should force the sdcard u-boot to be used

or if you can boot from emmc (with out an sdcard), just us dd to zero the emmc then the sdcard should boot without using the S2 button.