Arago on Beaglebone Black

Hi Curtis,

There is a function inside U-Boot board file - board_is_bone_lt(). It checks if the header.name is "A335BNLT", which is BeagleBone Black. This function is used for the DDR3 initialization.

However I'm not able to see this kind of check inside the Linux board file, which is strange. Please check this patch out.

I don't know when a new SDK version will be released.

Best regards,
Miroslav

Do you have an estimated release time for the BBB?

Work is being done right now for BBB support in the 06.00.00.00 SDK. Stay tuned.

Steve K.

I am looking forward for the 06.00.00.00 release. I would really like to make usage of the PM suspend to ram functionality on the Beagle Bone Black.

Regards,

Mathijs van den Berg

The new SDK will be supporting BBB and it should be ready by first week of July.

Out of curiosity, are you staying with the 3.2 kernel? The 3.8 kernel shipped with the BBB is all new and shiny and all, but I don't think the support for AM335x hardware crypto support is in there yet. 

Yes, the next SDK will be based on 3.2

Dear TI,

I see that the 6.0 SDK is released. However when i check the 'http://www.ti.com/tool/linuxezsdk-sitara' page, the link for Beaglebone redirects to the Beagleboard XM

page, which contains a link with a 3.3.7 kernel that wont boot on my Beaglebone Black. Where can i find the correct SDK sources/binaries for the Beaglebone Black?

Regards,

Mathijs

Hi,

Here it is: http://downloads.ti.com/sitara_linux/esd/AM335xSDK/latest/index_FDS.html

Best regards,
Miroslav

Hi Miroslav

I installed this SDK, create a sd-card with script on bin directory, but my BBB doesn't boot!

I remove the MLO file from bbb boot directory to be sure to boot on sd-card.

The only thing I see now it the boot partition from sd-card, with the 3 files and device is called "netchip mass storage gadget".

Do we need to do something special or what I did wrong?

Thanks for you help.

Greg

Hi,

The BBB doesn't have an on-board FTDI chip in order to reduce the end-product price. Do you have access to a FTDI cable (or a RS232 level translator) which you can connect to the UART0 pins, located on the J1 connector? I believe your BeagleBone Black is stuck in U-Boot for some reason. Most probably something related to the U-Boot environment.

Try holding the "User Boot" button (S2) while applying power to the BBB and see if this helps.

If it doesn't, then you can try to create a uEnv.txt file with the following content inside the /root partition of the SD card:

arch=arm
baudrate=115200
board=am335x
board_name=A335BNLT
board_rev=0A5B
bootcmd=gpio set 53; i2c mw 0x24 1 0x3e; mmc dev 0; if mmc rescan ; then echo micro SD card found;setenv mmcdev 0;else echo No micro SD card found, setting mmcdev to 1;setenv mmcdev 1;fi;setenv bootpart ${mmcdev}:2;mmc dev ${mmcdev}; if mmc rescan; then gpio set 54; echo SD/MMC found on device ${mmcdev};if run loadbootenv; then echo Loaded environment from ${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;gpio set 55; if run loaduimage; then gpio set 56; run mmcboot;fi;fi;
bootdelay=1
bootdir=/boot
bootenv=uEnv.txt
bootfile=uImage
bootpart=0:2
console=ttyO0,115200n8
cpu=armv7
dfu_alt_info_emmc=rawemmc mmc 0 3751936
dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw mmc 100 100;u-boot.img.raw mmc 300 3C0;u-boot.img fat 0 1;uEnv.txt fat 0 1
dfu_alt_info_nand=SPL part 0 1;SPL.backup1 part 0 2;SPL.backup2 part 0 3;SPL.backup3 part 0 4;u-boot part 0 5;kernel part 0 7;rootfs part 0 8
ethact=cpsw
ethaddr=90:59:af:5f:5b:1b
importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesize
kloadaddr=0x80007fc0
loadaddr=0x80200000
loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}
loadramdisk=load mmc ${mmcdev} ${rdaddr} ramdisk.gz
loaduimage=load mmc ${bootpart} ${kloadaddr} ${bootdir}/${bootfile}
mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot} rootfstype=${mmcrootfstype}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${kloadaddr}
mmcdev=0
mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext3 rootwait
mtdids=nand0=omap2-nand.0
mtdparts=mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1920k(u-boot),128k(u-boot-env),5m(kernel),-(rootfs)
nandargs=setenv bootargs console=${console} ${optargs} root=${nandroot} rootfstype=${nandrootfstype}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} ${nandsrcaddr} ${nandimgsize}; bootm ${loadaddr}
nandimgsize=0x500000
nandroot=ubi0:rootfs rw ubi.mtd=7,2048
nandrootfstype=ubifs rootwait=1
nandsrcaddr=0x280000
netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp
netboot=echo Booting from network ...; setenv autoload no; dhcp; tftp ${loadaddr} ${bootfile}; run netargs; bootm ${loadaddr}
nfsopts=nolock
ramargs=setenv bootargs console=${console} ${optargs} root=${ramroot} rootfstype=${ramrootfstype}
ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr} ${rdaddr}
ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=${rdaddr},64M
ramrootfstype=ext2
rdaddr=0x81000000
rootpath=/export/rootfs
soc=am33xx
spiargs=setenv bootargs console=${console} ${optargs} root=${spiroot} rootfstype=${spirootfstype}
spiboot=echo Booting from spi ...; run spiargs; sf probe ${spibusno}:0; sf read ${loadaddr} ${spisrcaddr} ${spiimgsize}; bootm ${loadaddr}
spibusno=0
spiimgsize=0x362000
spiroot=/dev/mtdblock4 rw
spirootfstype=jffs2
spisrcaddr=0xe0000
static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
stderr=serial
stdin=serial
stdout=serial
usbnet_devaddr=90:59:af:5f:5b:1b
vendor=ti
ver=U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

Then try powering the board again with the S2 button pressed.

Best regards,
Miroslav

Hi manager，

   I try to suspend the beaglebone black with command “echo mem >/sys/power/state”, but nothing happened. Then I checked the APM with "cat /sys/power/state",nothing has been shown. However I'm sure I have add APM choice in kernel 3.8.6.

 Someone say must load am335x-firmware.bin,and someone say wait for sdk 6.00.00.00,kernel 3.2 will support.

Unfortunately, I have try the sdk 6.00.00.00,but failed.

 What should I do?How can I suspend with the BBB board?

Dear Chancen Guo,

I see that you would like to suspend your BBB running kernel 3.8.6. As far as i know, this is not possible yet.

The SDK 6.00.00.00 for BBB comes with the 3.2 kernel included, as suspend works like a charm (tested myself).

Please try the 'board-support-bin' pre-built-images for fast results.

after that, you can use 'echo standby > /sys/power/state'

Good luck!

Mathijs

Dear Mathijs

       Thanks for your reply.  I have followed your suggestion,unfortunately,I failed.

        I used e 'board-support-bin' pre-built-images', but the board can't start.

       The message is as following:

U-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
mmc0 is current device
SD/MMC found on device 0
reading uEnv.txt
14 bytes read in 4 ms (2.9 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
reading uImage
** Unable to read file uImage **
4223640 bytes read in 641 ms (6.3 MiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.8.6
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4223576 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).

Available machine support:

ID (hex)        NAME
ffffffff        Generic OMAP4 (Flattened Device Tree)
ffffffff        Generic AM33XX (Flattened Device Tree)
ffffffff        Generic OMAP3-GP (Flattened Device Tree)
ffffffff        Generic OMAP3 (Flattened Device Tree)
0000060a        OMAP3 Beagle Board
00000a9d        IGEP OMAP3 module
00000928        IGEP v2 board
00000ae7        OMAP4 Panda board

Please check your kernel config and/or bootloader.

What should I do?

Chancen

I can see that you are trying to boot kernel 3.8.6.

Like i noted in my previous post, the 3.8.6 is not ready yet for power management due to device tree/platform data driver. (as far as i know..)

Therefore your only chances for now is the 6.00.00 SDK.

http://downloads.ti.com/sitara_linux/esd/AM335xSDK/latest/exports/am335x-evm-sdk-bin-06.00.00.00.tar.gz

This package contains the 3.2 kernel / u-boot / MLO together with a matching rootfs.

Good luck!

Dear Mathijs,

        So much thanks for your help! Following your suggestion,now the BBB can run perfectly.

       I try "echo mem >/sys/power/state", it show as following:

      root@am335x-evm:/# echo mem >/sys/power/state    
[   62.336059] PM: Syncing filesystems ...
[   65.818725] done.
[   65.897796] Freezing user space processes ... (elapsed 0.01 seconds) done.
[   65.918609] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[   65.938629] Suspending console(s) (use no_console_suspend to debug)

Does the machine suspend right? If it suspend correctly, how can I resume it?

What should I do?

I have a question about the 3.8 kernel.

I have had good success using the 6.00.00.00 version of the SDK on the BeagleBone, and using the instructions here (thanks!) even got that image to work on the BBB.

Unfortunately, there is no HDMI support that I was able to track down.

The use that I am investigating is using a BBB with an attached LCD to play videos driven by our software. I prototyped it out using "mplayer", and it seems to work well, but the linux 3.8 kernel that I rebuilt does not have any powerVR support. I was able to rebuild the PowerVR stuff (Graphics_SDK_4_10_00_01) against linux 3.8 but I haven't gotten it to show anything out the HDMI.

So, is there a new version of the LINUXEZ SDK coming, supporting the onboard HDMI of the BBB *and* the PowerVR chip? I thought I saw a rumor to that effect.

Thanks!

Kelton

Kelton,

our SDK will be supporting BeagleBone Black in 1Q14.

Hi There all developers,

I am using BBB revision A5A, I am following the posts and ended up with some junk characters on minicom console

FYI: using "ti-sdk-am335x-evm-06.00.00.00-Linux-x86-Install" provided by TI

minicom setup details are as follows:

A -    Serial Device      : /dev/ttyUSB0
B - Lockfile Location     : /var/lock
C -   Callin Program      :               
D -  Callout Program      :              
E -    Bps/Par/Bits       : 115200 8N1
F - Hardware Flow Control : No       
G - Software Flow Control : No        

presuming baud rate is the problem, i have tried with all the combination of baud rate and ended up with same result ( junk characters) 

output on minicom console :

attached files are the output of minicom

Kindly someone help me out from this!!!

Thanks & Regards

Ranjan.D

Bangalore

Thank you!

Kelton

Ranjan,

Please start a new tread regarding your question.

Hi all,

I was reading the thread. I want to confirm this conclusion I have made:

Is BBB with linux kernel version 3.8+ is still not available with power management??

Thank you.

Our current SDK is based on 3.2.

If you want more details about 3.8, please post your question at beaglebone.org