Linux/AM3358: SDK setup

Hello Kenneth,

No. If you saw the "Killed by signal 1" and "Hanging up" messages in minicom that is expected to be seen. You can continue to follow the next steps.

Best regards,
Kemal

Hi Kemal,

I did not see either of those messages in minicom. What I saw was actual serial junk, the kind of characters that you would typically see during a baud rate mismatch.

Here is a section of the output:

After successfully executing this script, your board will be set up. You will be
able to connect to it by executing 'minicom -w' or if you prefer a windows host
you can set up Tera Term as explained in the Software Developer's Guide.
If you connect minicom or Tera Term and power cycle the board Linux will boot.

[ y ] y

Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB0, 11:09:28

Press CTRL-A Z for help on special keys

��Uk����������{�k�����w��������oo�������kkW{}mowï

What if you simply run minicom -D /dev/ttyUSBX or picocom --baud 115200 /dev/ttyUSBX command. Do these characters still appear?

I still see the same characters when I run the commands you mentioned and the BBB is booting.

This is strange. Can you first try making different combinations and try to find out whether the host PC, BBB or tty to USB cable is causing this behavior?

Just tried a different BBB, same Issue, doubt there's anything wrong with my PC, hasn't given me trouble for similar stuff before.

Maybe it's the cable? Or could it be some issue with the serial port settings (parity, stop bits)? The cable I am using is similar to https://www.adafruit.com/product/70 as recommended in https://elinux.org/Beagleboard:BeagleBone_Black_Accessories#Serial_Debug_Cables

Unfortunately don't have any spares on hand right now.

Kenneth Joel said:

Maybe it's the cable?

Kenneth Joel said:

Or could it be some issue with the serial port settings (parity, stop bits)?

I am using a mini USB cable to power the board

Here's my picocom output

kenneth@kenneth-HP-Pavilion-Notebook:~$ picocom --baud 115200 /dev/ttyUSB0
picocom v1.7

port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv
imap is :
omap is :
emap is : crcrlf,delbs,

Terminal ready
��������������������������}�������������������������w}

Hi Kemal

Serial communication is up and running now, guess it was the grounding. Tested it out by logging in and trying out the Rpmsg quick start guide.

Thanks for all the help!

Resuming my SDK setup now, running setup script as specified in section 1.1.5 for the software developer's guide.

Reached the last part (creation of minicom script), unfortunately it is unable to detect the beaglebone.

The message 'No Beaglebone (Black) or Starterkit detected. Assuming general purpose evm is being used'

Is this expected? The last time I ran the setup script it was able to detect my BBB.

It detects it through lsusb command. Please, see the check_for_beaglebone() function in <Processor SDK>/bin/setup-uboot-env.sh file.

Yes, this is my lsusb output.

kenneth@kenneth-HP-Pavilion-Notebook:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd
Bus 001 Device 014: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 015: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Don't think any of these are the right ones.

You need to change the 0403:6001 to 10c4:ea60 and FTDI to cp210x in the <Processor SDK>/bin/setup-uboot-env.sh and <Processor SDK>/bin/common.sh files. Please, refer to this and this thread for more details.

Thanks Kemal! This really helped. The script ran to completion and a file named 'uboot.env' was placed in the boot partition of the board.

Okay. You can mark the thread as resolved by clicking on "This resolved my issue" button, once you successfully setup the SDK.