Is this the correct list for AM3517 EVM questions?

Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

Hello,
   I have a LogicPD Zoom AM3517 experimenters board.  Is this the 
correct list to ask questions about getting Yocto-based software running 
on this board?

Steven G

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
> Hello,
>   I have a LogicPD Zoom AM3517 experimenters board.  Is this the
> correct list to ask questions about getting Yocto-based software
> running on this board?

Yes, this is one of the correct lists for asking questions about AM3517 board 
when used with the Yocto Project. :) As this is the mailing list for meta-ti, 
which is the official Texas Instruments BSP layer for OpenEmbedded-Core and 
the Yocto Project, and AM3517 is currently one of the supported platforms in 
meta-ti.

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Khem Raj]

On Mar 19, 2013, at 10:21 AM, Denys Dmytriyenko <denys@ti.com> wrote:

> On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
>> Hello,
>>  I have a LogicPD Zoom AM3517 experimenters board.  Is this the
>> correct list to ask questions about getting Yocto-based software
>> running on this board?
> 
> Yes, this is one of the correct lists for asking questions about AM3517 board 
> when used with the Yocto Project. :) As this is the mailing list for meta-ti, 
> which is the official Texas Instruments BSP layer for OpenEmbedded-Core and 
> the Yocto Project, and AM3517 is currently one of the supported platforms in 
> meta-ti.

Now question please :)

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
> On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
>> Hello,
>>    I have a LogicPD Zoom AM3517 experimenters board.  Is this the
>> correct list to ask questions about getting Yocto-based software
>> running on this board?
> Yes, this is one of the correct lists for asking questions about AM3517 board
> when used with the Yocto Project. :) As this is the mailing list for meta-ti,
> which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
> the Yocto Project, and AM3517 is currently one of the supported platforms in
> meta-ti.
>
Wonderful.  Can someone point me to information so that I can build a 
system using the Yocto project and program an SD card with the necessary 
files to boot my board into Linux?

   With all of the S7 DIP switches in the off position (which the AM3517 
Development Kits User Manual indicates is the default boot from NAND) I 
don't get any output from the serial UART so my guess is that I've hosed 
the NAND.

   For debugging support I have a TI Stellaris LM3S8962 board which has 
the ability to act as a JTAG debugger to external hardware.  For 
software I have OpenOCD 0.6.1

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Tue, Mar 19, 2013 at 02:08:52PM -0400, Steven Grunza wrote:
> On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
> >On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
> >>Hello,
> >>   I have a LogicPD Zoom AM3517 experimenters board.  Is this the
> >>correct list to ask questions about getting Yocto-based software
> >>running on this board?
> >Yes, this is one of the correct lists for asking questions about AM3517 board
> >when used with the Yocto Project. :) As this is the mailing list for meta-ti,
> >which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
> >the Yocto Project, and AM3517 is currently one of the supported platforms in
> >meta-ti.
> >
> Wonderful.  Can someone point me to information so that I can build
> a system using the Yocto project and program an SD card with the
> necessary files to boot my board into Linux?
> 
>   With all of the S7 DIP switches in the off position (which the
> AM3517 Development Kits User Manual indicates is the default boot
> from NAND) I don't get any output from the serial UART so my guess
> is that I've hosed the NAND.
> 
>   For debugging support I have a TI Stellaris LM3S8962 board which
> has the ability to act as a JTAG debugger to external hardware.  For
> software I have OpenOCD 0.6.1

I would assume you already checked this Hardware Setup page:
http://processors.wiki.ti.com/index.php/GSG:_AM35x_EVM_Hardware_Setup

Then you would need to check the Boot from SD/MMC page:
http://processors.wiki.ti.com/index.php/AM35x_EVM_Boot_from_SD/MMC_card

As of the software load, you can build a minimal rootfs image (e.g. 
core-image-minimal) with all the BSP components and setup an SD card as 
described above. You'll get the MLO, u-boot, uImage and rootfs as the
output of the build, that you need to load on to the card.

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

[-- Attachment #1: Type: text/plain, Size: 11103 bytes --]

On 3/19/2013 2:27 PM, Denys Dmytriyenko wrote:
> On Tue, Mar 19, 2013 at 02:08:52PM -0400, Steven Grunza wrote:
>> On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
>>> On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
>>>> Hello,
>>>>    I have a LogicPD Zoom AM3517 experimenters board.  Is this the
>>>> correct list to ask questions about getting Yocto-based software
>>>> running on this board?
>>> Yes, this is one of the correct lists for asking questions about AM3517 board
>>> when used with the Yocto Project. :) As this is the mailing list for meta-ti,
>>> which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
>>> the Yocto Project, and AM3517 is currently one of the supported platforms in
>>> meta-ti.
>>>
>> Wonderful.  Can someone point me to information so that I can build
>> a system using the Yocto project and program an SD card with the
>> necessary files to boot my board into Linux?
>>
>>    With all of the S7 DIP switches in the off position (which the
>> AM3517 Development Kits User Manual indicates is the default boot
>> from NAND) I don't get any output from the serial UART so my guess
>> is that I've hosed the NAND.
>>
>>    For debugging support I have a TI Stellaris LM3S8962 board which
>> has the ability to act as a JTAG debugger to external hardware.  For
>> software I have OpenOCD 0.6.1
> I would assume you already checked this Hardware Setup page:
> http://processors.wiki.ti.com/index.php/GSG:_AM35x_EVM_Hardware_Setup
>
> Then you would need to check the Boot from SD/MMC page:
> http://processors.wiki.ti.com/index.php/AM35x_EVM_Boot_from_SD/MMC_card
>
> As of the software load, you can build a minimal rootfs image (e.g.
> core-image-minimal) with all the BSP components and setup an SD card as
> described above. You'll get the MLO, u-boot, uImage and rootfs as the
> output of the build, that you need to load on to the card.
To what should I have MACHINE set?  Using beagleboard didn't work.

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp    = "<unknown>:<unknown>"


/home/yocto/poky-danny-8.0/build/tmp/deploy/images

-rw-r--r-- 1 grunzasr grunzasr   84719488 Mar 20 09:58 
core-image-minimal-beagleboard-20130320134504.rootfs.jffs2
-rw-r--r-- 1 grunzasr grunzasr  228538001 Mar 20 09:55 
core-image-minimal-beagleboard-20130320134504.rootfs.tar.bz2
lrwxrwxrwx 1 grunzasr grunzasr         60 Mar 20 09:57 
core-image-minimal-beagleboard.tar.bz2 -> 
core-image-minimal-beagleboard-20130320134504.rootfs.tar.bz2
-rw-r--r-- 1 grunzasr grunzasr 1538239488 Feb 26 14:57 
core-image-minimal-qemuppc-20130226141438.rootfs.ext3
-rw-r--r-- 1 grunzasr grunzasr  304174285 Feb 26 14:51 
core-image-minimal-qemuppc-20130226141438.rootfs.tar.bz2
-rw-r--r-- 1 grunzasr grunzasr 1538239488 Feb 26 16:20 
core-image-minimal-qemuppc-20130226210235.rootfs.ext3
-rw-r--r-- 1 grunzasr grunzasr  304179924 Feb 26 16:14 
core-image-minimal-qemuppc-20130226210235.rootfs.tar.bz2
lrwxrwxrwx 1 grunzasr grunzasr         53 Feb 26 16:20 
core-image-minimal-qemuppc.ext3 -> 
core-image-minimal-qemuppc-20130226210235.rootfs.ext3
lrwxrwxrwx 1 grunzasr grunzasr         56 Feb 26 16:17 
core-image-minimal-qemuppc.tar.bz2 -> 
core-image-minimal-qemuppc-20130226210235.rootfs.tar.bz2
-rw-r--r-- 1 grunzasr grunzasr  537657344 Mar 13 20:13 
core-image-sato-beagleboard-20130313180702.rootfs.jffs2
-rw-r--r-- 1 grunzasr grunzasr  343428455 Mar 13 20:07 
core-image-sato-beagleboard-20130313180702.rootfs.tar.bz2
lrwxrwxrwx 1 grunzasr grunzasr         55 Mar 13 20:13 
core-image-sato-beagleboard.jffs2 -> 
core-image-sato-beagleboard-20130313180702.rootfs.jffs2
lrwxrwxrwx 1 grunzasr grunzasr         57 Mar 13 20:11 
core-image-sato-beagleboard.tar.bz2 -> 
core-image-sato-beagleboard-20130313180702.rootfs.tar.bz2
-rw-r--r-- 1 grunzasr grunzasr 2488386560 Feb 26 20:16 
core-image-sato-qemuppc-20130226222738.rootfs.ext3
-rw-r--r-- 1 grunzasr grunzasr  483216390 Feb 26 20:05 
core-image-sato-qemuppc-20130226222738.rootfs.tar.bz2
lrwxrwxrwx 1 grunzasr grunzasr         50 Feb 26 20:16 
core-image-sato-qemuppc.ext3 -> 
core-image-sato-qemuppc-20130226222738.rootfs.ext3
lrwxrwxrwx 1 grunzasr grunzasr         53 Feb 26 20:10 
core-image-sato-qemuppc.tar.bz2 -> 
core-image-sato-qemuppc-20130226222738.rootfs.tar.bz2
lrwxrwxrwx 1 grunzasr grunzasr         70 Mar 13 19:54 MLO-beagleboard 
-> MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0*
-rwxr-xr-x 1 grunzasr grunzasr      22036 Mar 13 19:54 
MLO-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0*
-rw-rw-r-- 1 grunzasr grunzasr   28375528 Mar 13 16:23 
modules-3.4.11-yocto-standard-r4.3-beagleboard.tgz
-rw-rw-r-- 1 grunzasr grunzasr   38056200 Feb 26 13:05 
modules-3.4.11-yocto-standard-r4.3-qemuppc.tgz
-rw-rw-r-- 1 grunzasr grunzasr        294 Mar 20 09:49 
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
lrwxrwxrwx 1 grunzasr grunzasr         81 Mar 13 20:13 
u-boot-beagleboard.bin -> 
u-boot-beagleboard-v2011.06+git16+b1af6f532e0d348b153d5c148369229d24af361a-r3.bin*
-rwxr-xr-x 1 grunzasr grunzasr     285272 Mar 13 20:13 
u-boot-beagleboard-v2011.06+git16+b1af6f532e0d348b153d5c148369229d24af361a-r3.bin*
lrwxrwxrwx 1 grunzasr grunzasr         81 Mar 13 20:13 u-boot.bin -> 
u-boot-beagleboard-v2011.06+git16+b1af6f532e0d348b153d5c148369229d24af361a-r3.bin*
lrwxrwxrwx 1 grunzasr grunzasr        138 Mar 13 16:23 uImage -> 
uImage-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3-beagleboard-20130313180702.bin
-rw-r--r-- 1 grunzasr grunzasr    4309216 Mar 13 16:23 
uImage-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3-beagleboard-20130313180702.bin
lrwxrwxrwx 1 grunzasr grunzasr        138 Mar 13 16:23 
uImage-beagleboard.bin -> 
uImage-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3-beagleboard-20130313180702.bin
lrwxrwxrwx 1 grunzasr grunzasr        135 Feb 26 13:05 vmlinux -> 
vmlinux-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_2+7833f1549c3d44cce8aea38b65cd501229aad492-r4.3-qemuppc-20130226141438.bin
-rw-r--r-- 1 grunzasr grunzasr   93038630 Feb 26 13:05 
vmlinux-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_2+7833f1549c3d44cce8aea38b65cd501229aad492-r4.3-qemuppc-20130226141438.bin
lrwxrwxrwx 1 grunzasr grunzasr        135 Feb 26 13:05 
vmlinux-qemuppc.bin -> 
vmlinux-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_2+7833f1549c3d44cce8aea38b65cd501229aad492-r4.3-qemuppc-20130226141438.bin
-rwxr-xr-x 1 grunzasr grunzasr      22036 Mar 13 19:54 
x-load-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0.bin.ift*
lrwxrwxrwx 1 grunzasr grunzasr         81 Mar 13 19:54 
x-load-beagleboard.bin.ift -> 
x-load-beagleboard-1.5.0+git1+9f94c6577e3a018b6b75cbe39f32bb331871f915-r0.bin.ift*

grunzasr@stm32dbg% ls -l /mnt
total 0
grunzasr@stm32dbg% sudo cp MLO-beagleboard /mnt
grunzasr@stm32dbg% sudo cp u-boot.bin /mnt
grunzasr@stm32dbg% sudo cp uImage /mnt
grunzasr@stm32dbg% sync
grunzasr@stm32dbg% ls -l /mnt
total 4516
-rwxr-xr-x 1 root root   22036 Mar 20 09:59 MLO-beagleboard*
-rwxr-xr-x 1 root root  285272 Mar 20 10:00 u-boot.bin*
-rwxr-xr-x 1 root root 4309216 Mar 20 10:00 uImage*
grunzasr@stm32dbg% sudo umount /mnt


With DIPSW7-1 & 4 on, others off I get "40X" on serial console then 
nothing else.

Using files built on what I can find from 
AM35x-OMAP35x-LINUX-PSP-04.02.00.07

grunzasr@stm32dbg% pwd
/home/am3517/AM35x-OMAP35x-LINUX-PSP-04.02.00.07/images
grunzasr@stm32dbg% ls -l
total 12
drwxr-xr-x 5 grunzasr grunzasr 4096 Apr 29  2011 boot-strap/
drwxr-xr-x 5 grunzasr grunzasr 4096 Apr 29  2011 kernel/
drwxr-xr-x 5 grunzasr grunzasr 4096 Apr 29  2011 u-boot/
grunzasr@stm32dbg% ls -l boot-strap/am3517/
total 20
-rw-r--r-- 1 grunzasr grunzasr 16700 May  3  2011 x-load.bin.ift
grunzasr@stm32dbg% ls -l kernel/am3517/
total 2968
-rw-r--r-- 1 grunzasr grunzasr 3037308 May  3  2011 uImage
grunzasr@stm32dbg% ls -l u-boot/am3517/
total 220
-rwxr-xr-x 1 grunzasr grunzasr 222196 May  3  2011 u-boot.bin*

grunzasr@stm32dbg% pwd
/home/am3517/AM35x-OMAP35x-LINUX-PSP-04.02.00.07/images
grunzasr@stm32dbg%
grunzasr@stm32dbg%
grunzasr@stm32dbg% ls -l /mnt
total 0
grunzasr@stm32dbg% sudo cp boot-strap/am3517/x-load.bin.ift /mnt/MLO
grunzasr@stm32dbg% sudo cp kernel/am3517/uImage /mnt
grunzasr@stm32dbg% sudo cp u-boot/am3517/u-boot.bin /mnt
grunzasr@stm32dbg% ls -l /mnt
total 3208
-rwxr-xr-x 1 root root   16700 Mar 20 10:13 MLO*
-rwxr-xr-x 1 root root  222196 Mar 20 10:13 u-boot.bin*
-rwxr-xr-x 1 root root 3037308 Mar 20 10:13 uImage*
grunzasr@stm32dbg% sync
grunzasr@stm32dbg% sudo umount /mnt

> This gets me much farther.  I get the following on the serial port:

40X?@C?H?U??Instruments X-Loader 1.51 (May  3 2011 - 19:22:25)
Starting X-loader on MMC
Reading boot sector

222196 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2010.06 (May 03 2011 - 19:24:19)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
AM3517EVM Board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  HW ECC [Kernel/FS layout] selected
512 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Die ID #1b7e0000000000000155daa60200c00f
Net:   davinci_emac_initialize
Ethernet PHY: GENERIC @ 0x00
DaVinci EMAC
Hit any key to stop autoboot:  0
AM3517_EVM #

>  From this I conclude that my hardware is at least partially functional, my SD card is compatible with the AM3517 board, my serial connection is functioning, and I have at least the basics of getting the bootloading code (MLO) and u-boot onto the card.

> I suspect I need to change something in the /home/yocto/poky-danny-8.0/build/conf/local.conf file (probably MACHINE) to specify the correct hardware. I also need to figure out how to get the root file system written to the second partition of my SD card.  I couldn't find that information on any of the above mentioned pages or on the pages to which they have links.  My SD card is partitioned like this:

grunzasr@stm32dbg% sudo fdisk -l /dev/sdd

Disk /dev/sdd: 3959 MB, 3959422976 bytes
122 heads, 62 sectors/track, 1022 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

    Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *        2048     2099199     1048576    c  W95 FAT32 (LBA)
/dev/sdd2         2099200     7733247     2817024   83  Linux





[-- Attachment #2: Type: text/html, Size: 16699 bytes --]

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Wed, Mar 20, 2013 at 10:23:34AM -0400, Steven Grunza wrote:
> On 3/19/2013 2:27 PM, Denys Dmytriyenko wrote:
> >On Tue, Mar 19, 2013 at 02:08:52PM -0400, Steven Grunza wrote:
> >>On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
> >>>On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
> >>>>Hello,
> >>>>   I have a LogicPD Zoom AM3517 experimenters board.  Is this the
> >>>>correct list to ask questions about getting Yocto-based software
> >>>>running on this board?
> >>>Yes, this is one of the correct lists for asking questions about AM3517 board
> >>>when used with the Yocto Project. :) As this is the mailing list for meta-ti,
> >>>which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
> >>>the Yocto Project, and AM3517 is currently one of the supported platforms in
> >>>meta-ti.
> >>>
> >>Wonderful.  Can someone point me to information so that I can build
> >>a system using the Yocto project and program an SD card with the
> >>necessary files to boot my board into Linux?
> >>
> >>   With all of the S7 DIP switches in the off position (which the
> >>AM3517 Development Kits User Manual indicates is the default boot
> >>from NAND) I don't get any output from the serial UART so my guess
> >>is that I've hosed the NAND.
> >>
> >>   For debugging support I have a TI Stellaris LM3S8962 board which
> >>has the ability to act as a JTAG debugger to external hardware.  For
> >>software I have OpenOCD 0.6.1
> >I would assume you already checked this Hardware Setup page:
> >http://processors.wiki.ti.com/index.php/GSG:_AM35x_EVM_Hardware_Setup
> >
> >Then you would need to check the Boot from SD/MMC page:
> >http://processors.wiki.ti.com/index.php/AM35x_EVM_Boot_from_SD/MMC_card
> >
> >As of the software load, you can build a minimal rootfs image (e.g.
> >core-image-minimal) with all the BSP components and setup an SD card as
> >described above. You'll get the MLO, u-boot, uImage and rootfs as the
> >output of the build, that you need to load on to the card.
> To what should I have MACHINE set?  Using beagleboard didn't work.

There is "am3517-evm" machine in meta-ti:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/conf/machine

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

[-- Attachment #1: Type: text/plain, Size: 4724 bytes --]

On 3/20/2013 1:54 PM, Denys Dmytriyenko wrote:
> On Wed, Mar 20, 2013 at 01:48:21PM -0400, Steven Grunza wrote:
>> On 3/20/2013 11:17 AM, Denys Dmytriyenko wrote:
>>> On Wed, Mar 20, 2013 at 10:23:34AM -0400, Steven Grunza wrote:
>>>> On 3/19/2013 2:27 PM, Denys Dmytriyenko wrote:
>>>>> On Tue, Mar 19, 2013 at 02:08:52PM -0400, Steven Grunza wrote:
>>>>>> On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
>>>>>>> On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
>>>>>>>> Hello,
>>>>>>>>    I have a LogicPD Zoom AM3517 experimenters board.  Is this the
>>>>>>>> correct list to ask questions about getting Yocto-based software
>>>>>>>> running on this board?
>>>>>>> Yes, this is one of the correct lists for asking questions about AM3517 board
>>>>>>> when used with the Yocto Project. :) As this is the mailing list for meta-ti,
>>>>>>> which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
>>>>>>> the Yocto Project, and AM3517 is currently one of the supported platforms in
>>>>>>> meta-ti.
>>>>>>>
>>>>>> Wonderful.  Can someone point me to information so that I can build
>>>>>> a system using the Yocto project and program an SD card with the
>>>>>> necessary files to boot my board into Linux?
>>>>>>
>>>>>>    With all of the S7 DIP switches in the off position (which the
>>>>>> AM3517 Development Kits User Manual indicates is the default boot
>>>>> >from NAND) I don't get any output from the serial UART so my guess
>>>>>> is that I've hosed the NAND.
>>>>>>
>>>>>>    For debugging support I have a TI Stellaris LM3S8962 board which
>>>>>> has the ability to act as a JTAG debugger to external hardware.  For
>>>>>> software I have OpenOCD 0.6.1
>>>>> I would assume you already checked this Hardware Setup page:
>>>>> http://processors.wiki.ti.com/index.php/GSG:_AM35x_EVM_Hardware_Setup
>>>>>
>>>>> Then you would need to check the Boot from SD/MMC page:
>>>>> http://processors.wiki.ti.com/index.php/AM35x_EVM_Boot_from_SD/MMC_card
>>>>>
>>>>> As of the software load, you can build a minimal rootfs image (e.g.
>>>>> core-image-minimal) with all the BSP components and setup an SD card as
>>>>> described above. You'll get the MLO, u-boot, uImage and rootfs as the
>>>>> output of the build, that you need to load on to the card.
>>>> To what should I have MACHINE set?  Using beagleboard didn't work.
>>> There is "am3517-evm" machine in meta-ti:
>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/conf/machine
>>>
>> What is the proper way to include the above file in my build
>> environment or is there a URL describing it that I've missed?
> You need to add meta-ti layer to your configuration. It can be as easy as
> git-cloning it into your sources location, along with other "meta" layers and
> adding it to your bblayers.conf file. You'd need to also add BBMASK to your
> local.conf, as described in meta-ti README file. After that you can build for
> MACHINE=am3517-evm
>

I did something wrong or missed a step.  I got:

grunzasr@stm32dbg:/home/yocto/poky-danny-8.0/build$ bitbake 
core-image-sato-sdk
Pseudo is not present but is required, building this first before the 
main build
Parsing recipes: 100% 
|#####################################################################################################| 
Time: 00:02:17
Parsing of 899 .bb files complete (0 cached, 899 parsed). 1205 targets, 
67 skipped, 7 masked, 0 errors.
ERROR: No recipes available for:
/home/yocto/poky-danny-8.0/meta-ti/recipes-graphics/mesa/mesa-dri_9.0.2.bbappend
ERROR: Command execution failed: Exited with 1

I put the meta-ti (via a git clone) into /home/yocto/poky-danny-8.0

grunzasr@stm32dbg:/home/yocto/poky-danny-8.0/build$ ls -l 
/home/yocto/poky-danny-8.0
total 72
drwxrwxr-x  6 grunzasr grunzasr  4096 Oct 22 19:03 bitbake
drwxrwxr-x  6 grunzasr grunzasr  4096 Mar 20 14:11 build
drwxrwxr-x 11 grunzasr grunzasr  4096 Oct 22 19:03 documentation
-rw-rw-r--  1 grunzasr grunzasr   545 Oct 22 19:03 LICENSE
drwxrwxr-x 21 grunzasr grunzasr  4096 Oct 22 19:03 meta
drwxrwxr-x  4 grunzasr grunzasr  4096 Oct 22 19:03 meta-hob
drwxrwxr-x  5 grunzasr grunzasr  4096 Oct 22 19:03 meta-skeleton
drwxr-xr-x 12 grunzasr grunzasr  4096 Mar 20 14:04 meta-ti
drwxrwxr-x  6 grunzasr grunzasr  4096 Oct 22 19:03 meta-yocto
drwxrwxr-x  9 grunzasr grunzasr  4096 Oct 22 19:03 meta-yocto-bsp
-rwxrwxr-x  1 grunzasr grunzasr  1531 Oct 22 19:03 oe-init-build-env
-rw-rw-r--  1 grunzasr grunzasr  2038 Oct 22 19:03 README
-rw-rw-r--  1 grunzasr grunzasr 17245 Oct 22 19:03 README.hardware
drwxrwxr-x  8 grunzasr grunzasr  4096 Oct 22 19:03 scripts

Is there another meta package I need?



[-- Attachment #2: Type: text/html, Size: 7036 bytes --]

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Wed, Mar 20, 2013 at 02:18:28PM -0400, Steven Grunza wrote:
> On 3/20/2013 1:54 PM, Denys Dmytriyenko wrote:
> >On Wed, Mar 20, 2013 at 01:48:21PM -0400, Steven Grunza wrote:
> >>On 3/20/2013 11:17 AM, Denys Dmytriyenko wrote:
> >>>On Wed, Mar 20, 2013 at 10:23:34AM -0400, Steven Grunza wrote:
> >>>>On 3/19/2013 2:27 PM, Denys Dmytriyenko wrote:
> >>>>>On Tue, Mar 19, 2013 at 02:08:52PM -0400, Steven Grunza wrote:
> >>>>>>On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
> >>>>>>>On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
> >>>>>>>>Hello,
> >>>>>>>>   I have a LogicPD Zoom AM3517 experimenters board.  Is this the
> >>>>>>>>correct list to ask questions about getting Yocto-based software
> >>>>>>>>running on this board?
> >>>>>>>Yes, this is one of the correct lists for asking questions about AM3517 board
> >>>>>>>when used with the Yocto Project. :) As this is the mailing list for meta-ti,
> >>>>>>>which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
> >>>>>>>the Yocto Project, and AM3517 is currently one of the supported platforms in
> >>>>>>>meta-ti.
> >>>>>>>
> >>>>>>Wonderful.  Can someone point me to information so that I can build
> >>>>>>a system using the Yocto project and program an SD card with the
> >>>>>>necessary files to boot my board into Linux?
> >>>>>>
> >>>>>>   With all of the S7 DIP switches in the off position (which the
> >>>>>>AM3517 Development Kits User Manual indicates is the default boot
> >>>>>>from NAND) I don't get any output from the serial UART so my guess
> >>>>>>is that I've hosed the NAND.
> >>>>>>
> >>>>>>   For debugging support I have a TI Stellaris LM3S8962 board which
> >>>>>>has the ability to act as a JTAG debugger to external hardware.  For
> >>>>>>software I have OpenOCD 0.6.1
> >>>>>I would assume you already checked this Hardware Setup page:
> >>>>>http://processors.wiki.ti.com/index.php/GSG:_AM35x_EVM_Hardware_Setup
> >>>>>
> >>>>>Then you would need to check the Boot from SD/MMC page:
> >>>>>http://processors.wiki.ti.com/index.php/AM35x_EVM_Boot_from_SD/MMC_card
> >>>>>
> >>>>>As of the software load, you can build a minimal rootfs image (e.g.
> >>>>>core-image-minimal) with all the BSP components and setup an SD card as
> >>>>>described above. You'll get the MLO, u-boot, uImage and rootfs as the
> >>>>>output of the build, that you need to load on to the card.
> >>>>To what should I have MACHINE set?  Using beagleboard didn't work.
> >>>There is "am3517-evm" machine in meta-ti:
> >>>http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/conf/machine
> >>>
> >>What is the proper way to include the above file in my build
> >>environment or is there a URL describing it that I've missed?
> >You need to add meta-ti layer to your configuration. It can be as easy as
> >git-cloning it into your sources location, along with other "meta" layers and
> >adding it to your bblayers.conf file. You'd need to also add BBMASK to your
> >local.conf, as described in meta-ti README file. After that you can build for
> >MACHINE=am3517-evm
> >
> 
> I did something wrong or missed a step.  I got:
> 
> grunzasr@stm32dbg:/home/yocto/poky-danny-8.0/build$ bitbake
> core-image-sato-sdk
> Pseudo is not present but is required, building this first before
> the main build
> Parsing recipes: 100% |#####################################################################################################|
> Time: 00:02:17
> Parsing of 899 .bb files complete (0 cached, 899 parsed). 1205
> targets, 67 skipped, 7 masked, 0 errors.
> ERROR: No recipes available for:
> /home/yocto/poky-danny-8.0/meta-ti/recipes-graphics/mesa/mesa-dri_9.0.2.bbappend
> ERROR: Command execution failed: Exited with 1
> 
> I put the meta-ti (via a git clone) into /home/yocto/poky-danny-8.0

If you are using poky-danny as a base, you need to use "danny" branch of 
meta-ti to match the versions.

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Robert P. J. Day]

On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:

... snip ...

> If you are using poky-danny as a base, you need to use "danny"
> branch of meta-ti to match the versions.

  i ordered that very AM3517 exp kit this morning and, while it's
in transit, i'm building a core-image-minimal for it. should i expect
success if i use the absolute latest "git pull"s of everything?

  i'm aware of the recipe masking issue and the mesa-dri version thing
so i won't trip over that. so far, the "fetchall" worked and i'm
currently on "running tasks (191 of 1591)" of the build itself.

  is there any reason to think this shouldn't finish? thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Wed, Mar 20, 2013 at 02:45:17PM -0400, Robert P. J. Day wrote:
> On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:
> 
> ... snip ...
> 
> > If you are using poky-danny as a base, you need to use "danny"
> > branch of meta-ti to match the versions.
> 
>   i ordered that very AM3517 exp kit this morning and, while it's
> in transit, i'm building a core-image-minimal for it. should i expect
> success if i use the absolute latest "git pull"s of everything?
> 
>   i'm aware of the recipe masking issue and the mesa-dri version thing
> so i won't trip over that. so far, the "fetchall" worked and i'm
> currently on "running tasks (191 of 1591)" of the build itself.
> 
>   is there any reason to think this shouldn't finish? thanks.

http://article.gmane.org/gmane.linux.embedded.yocto.meta-ti/1661

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Wed, Mar 20, 2013 at 02:57:47PM -0400, Denys Dmytriyenko wrote:
> On Wed, Mar 20, 2013 at 02:45:17PM -0400, Robert P. J. Day wrote:
> > On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:
> > 
> > ... snip ...
> > 
> > > If you are using poky-danny as a base, you need to use "danny"
> > > branch of meta-ti to match the versions.
> > 
> >   i ordered that very AM3517 exp kit this morning and, while it's
> > in transit, i'm building a core-image-minimal for it. should i expect
> > success if i use the absolute latest "git pull"s of everything?
> > 
> >   i'm aware of the recipe masking issue and the mesa-dri version thing
> > so i won't trip over that. so far, the "fetchall" worked and i'm
> > currently on "running tasks (191 of 1591)" of the build itself.
> > 
> >   is there any reason to think this shouldn't finish? thanks.
> 
> http://article.gmane.org/gmane.linux.embedded.yocto.meta-ti/1661

Oh, and "danny" results are on the meta-arago mailing list, although those are 
for the entire SDK, but much more green overall... :)

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Robert P. J. Day]

On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:

> On Wed, Mar 20, 2013 at 02:45:17PM -0400, Robert P. J. Day wrote:
> > On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:
> >
> > ... snip ...
> >
> > > If you are using poky-danny as a base, you need to use "danny"
> > > branch of meta-ti to match the versions.
> >
> >   i ordered that very AM3517 exp kit this morning and, while it's
> > in transit, i'm building a core-image-minimal for it. should i expect
> > success if i use the absolute latest "git pull"s of everything?
> >
> >   i'm aware of the recipe masking issue and the mesa-dri version thing
> > so i won't trip over that. so far, the "fetchall" worked and i'm
> > currently on "running tasks (191 of 1591)" of the build itself.
> >
> >   is there any reason to think this shouldn't finish? thanks.
>
> http://article.gmane.org/gmane.linux.embedded.yocto.meta-ti/1661

  i should probably pay more attention to that. :-(

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]

On 3/20/2013 3:58 PM, Robert P. J. Day wrote:
> On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:
>
>> On Wed, Mar 20, 2013 at 02:45:17PM -0400, Robert P. J. Day wrote:
>>> On Wed, 20 Mar 2013, Denys Dmytriyenko wrote:
>>>
>>> ... snip ...
>>>
>>>> If you are using poky-danny as a base, you need to use "danny"
>>>> branch of meta-ti to match the versions.
>>>    i ordered that very AM3517 exp kit this morning and, while it's
>>> in transit, i'm building a core-image-minimal for it. should i expect
>>> success if i use the absolute latest "git pull"s of everything?
>>>
>>>    i'm aware of the recipe masking issue and the mesa-dri version thing
>>> so i won't trip over that. so far, the "fetchall" worked and i'm
>>> currently on "running tasks (191 of 1591)" of the build itself.
>>>
>>>    is there any reason to think this shouldn't finish? thanks.
>> http://article.gmane.org/gmane.linux.embedded.yocto.meta-ti/1661
>
So the build finished and I loaded the files onto my SD card.  MLO, 
u-boot.img, and uImage onto the first partition.  I untarred the root 
file system onto the second partition.  This is the result on the serial 
console:

40X?H?????SPL 2011.12-dirty (Mar 21 2013 - 19:36:59)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.12-dirty (Mar 21 2013 - 19:36:59)

AM35XX-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
AM3517EVM Board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Die ID #1b7e0000000000000155daa60200c00f
Hit any key to stop autoboot:  0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

3160284 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
    Image Name:   Linux-2.6.37
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    3160220 Bytes = 3 MiB
    Load Address: 80008000
    Entry Point:  80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
OK

Starting kernel ...


Did I miss a step?

[-- Attachment #2: Type: text/html, Size: 3690 bytes --]

Re: Is this the correct list for AM3517 EVM questions?

[Robert P. J. Day]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1935 bytes --]

On Tue, 26 Mar 2013, Steven Grunza wrote:

... snip ...

> So the build finished and I loaded the files onto my SD card.  MLO,
> u-boot.img, and uImage onto the first partition.  I untarred the
> root file system onto the second partition.  This is the result on
> the serial console:
>
> 40X???H????????????сSPL 2011.12-dirty (Mar 21 2013 - 19:36:59)
> Texas Instruments Revision detection unimplemented
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2011.12-dirty (Mar 21 2013 - 19:36:59)
>
> AM35XX-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
> AM3517EVM Board + LPDDR/NAND
> I2C:   ready
> DRAM:  256 MiB
> NAND:  512 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - bad CRC, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Die ID #1b7e0000000000000155daa60200c00f
> Hit any key to stop autoboot:  0
> reading boot.scr
>
> ** Unable to read "boot.scr" from mmc 0:1 **
> reading uImage
>
> 3160284 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 82000000 ...
>    Image Name:   Linux-2.6.37
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3160220 Bytes = 3 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Did I miss a step?

  that was going to be my long weekend project ... are you saying it
just hung at that point?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

[-- Attachment #1: Type: text/plain, Size: 3387 bytes --]

On 3/26/2013 5:18 PM, Robert P. J. Day wrote:
> On Tue, 26 Mar 2013, Steven Grunza wrote:
>
> ... snip ...
>
>> So the build finished and I loaded the files onto my SD card.  MLO,
>> u-boot.img, and uImage onto the first partition.  I untarred the
>> root file system onto the second partition.  This is the result on
>> the serial console:
>>
>> 40X???H????????????сSPL 2011.12-dirty (Mar 21 2013 - 19:36:59)
>> Texas Instruments Revision detection unimplemented
>> OMAP SD/MMC: 0
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2011.12-dirty (Mar 21 2013 - 19:36:59)
>>
>> AM35XX-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
>> AM3517EVM Board + LPDDR/NAND
>> I2C:   ready
>> DRAM:  256 MiB
>> NAND:  512 MiB
>> MMC:   OMAP SD/MMC: 0
>> *** Warning - bad CRC, using default environment
>>
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Die ID #1b7e0000000000000155daa60200c00f
>> Hit any key to stop autoboot:  0
>> reading boot.scr
>>
>> ** Unable to read "boot.scr" from mmc 0:1 **
>> reading uImage
>>
>> 3160284 bytes read
>> Booting from mmc ...
>> ## Booting kernel from Legacy Image at 82000000 ...
>>     Image Name:   Linux-2.6.37
>>     Image Type:   ARM Linux Kernel Image (uncompressed)
>>     Data Size:    3160220 Bytes = 3 MiB
>>     Load Address: 80008000
>>     Entry Point:  80008000
>>     Verifying Checksum ... OK
>>     Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Did I miss a step?
>    that was going to be my long weekend project ... are you saying it
> just hung at that point?
>
> rday
>
Yes.  Just hung. Here's a little more info on my system.  I changed the 
loadaddr environment variable to match the reported load address from 
u-boot reading the uImage file.  Saving the new value fixed the "*** 
Warning - bad CRC, using default environment" message.


40X?@C?UI??сSPL 2011.12-dirty (Mar 21 2013 - 19:36:59)
Texas Instruments Revision detection unimplemented
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.12-dirty (Mar 21 2013 - 19:36:59)

AM35XX-GP ES1.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 Mhz
AM3517EVM Board + LPDDR/NAND
I2C:   ready
DRAM:  256 MiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0
In:    serial
Out:   serial
Err:   serial
Die ID #1b7e0000000000000155daa60200c00f
Hit any key to stop autoboot:  0
AM3517_EVM # printenv
baudrate=115200
bootcmd=if mmc rescan ${mmcdev}; then if run loadbootscript; then run 
bootscript; else
if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run 
nandboot; fi
bootdelay=10
bootfile=uImage
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
console=ttyO2,115200n8
dieid#=1b7e0000000000000155daa60200c00f
loadaddr=80008000
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw 
rootfstype=ext3 rootw
ait
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
mmcdev=0
nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw 
rootfstype=jffs2
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 
280000 400000;
  bootm ${loadaddr}
stderr=serial
stdin=serial
stdout=serial

Environment size: 911/131068 bytes
AM3517_EVM #




[-- Attachment #2: Type: text/html, Size: 4457 bytes --]

Re: Is this the correct list for AM3517 EVM questions?

[Robert P. J. Day]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1510 bytes --]

On Tue, 26 Mar 2013, Steven Grunza wrote:

... snip ...

>    Image Name:   Linux-2.6.37
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3160220 Bytes = 3 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Did I miss a step?
>
>   that was going to be my long weekend project ... are you saying it
> just hung at that point?
>
> rday
>
> Yes.  Just hung. Here's a little more info on my system.  I changed
> the loadaddr environment variable to match the reported load address
> from u-boot reading the uImage file.  Saving the new value fixed the
> "*** Warning - bad CRC, using default environment" message.

  finally had time to test and had exactly the same result: "Starting
kernel ..." and ... hang.

  thoughts, anyone? i have the bootable SD card that came with the kit
from logicpd so i'll try to identify some critical difference.

rday

p.s.  this is building a core-image-minimal for an am3517-evm.

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

On 3/27/2013 3:40 PM, Robert P. J. Day wrote:
> On Tue, 26 Mar 2013, Steven Grunza wrote:
>
> ... snip ...
>
>>     Image Name:   Linux-2.6.37
>>     Image Type:   ARM Linux Kernel Image (uncompressed)
>>     Data Size:    3160220 Bytes = 3 MiB
>>     Load Address: 80008000
>>     Entry Point:  80008000
>>     Verifying Checksum ... OK
>>     Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Did I miss a step?
>>
>>    that was going to be my long weekend project ... are you saying it
>> just hung at that point?
>>
>> rday
>>
>> Yes.  Just hung. Here's a little more info on my system.  I changed
>> the loadaddr environment variable to match the reported load address
>> from u-boot reading the uImage file.  Saving the new value fixed the
>> "*** Warning - bad CRC, using default environment" message.
>    finally had time to test and had exactly the same result: "Starting
> kernel ..." and ... hang.
>
>    thoughts, anyone? i have the bootable SD card that came with the kit
> from logicpd so i'll try to identify some critical difference.
>
> rday
>
> p.s.  this is building a core-image-minimal for an am3517-evm.
>
Wow!  You got the SD card?  The kit was supposed to come with a Windows 
CE and a Linux SD card but I didn't get either.  I was never able to get 
LogicPD support to send me the image, either.  They just kept pointing 
the the procedures spread all over the web on how to build the code.

I built core-image-base for the am3517-evm.

Re: Is this the correct list for AM3517 EVM questions?

[Robert P. J. Day]

On Wed, 27 Mar 2013, Steven Grunza wrote:

> Wow!  You got the SD card?  The kit was supposed to come with a
> Windows CE and a Linux SD card but I didn't get either.  I was never
> able to get LogicPD support to send me the image, either.  They just
> kept pointing the the procedures spread all over the web on how to
> build the code.

  just to establish a foundation here, this is the result of booting
from the SD card that came with the board from logicpd:

=====start=====
...
218976 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2009.11 (Jan 22 2011 - 01:45:10)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
AM3517EVM Board + LPDDR/NAND
I2C:   ready
DRAM:  256 MB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Die ID #40be00010000000001685a2001015021
Net:   davinci_emac_initialize
Ethernet PHY: GENERIC @ 0x00
DaVinci EMAC
Hit any key to stop autoboot:  0
mmc1 is available
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

2308136 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Arago/2.6.32-psp03.00.01.06.sdk/
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2308072 Bytes =  2.2 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing
Linux.................................................................................................
Linux version 2.6.32 (schuyler_2@neo) (gcc version 4.3.3 (Sourcery G++
Lite 2009q1-203) ) #1 Tue Jan 25 16:18:32 CS1
CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3517/AM3517 EVM
Memory policy: ECC disabled, Data cache writeback
AM3517 ES3.1 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 4194304 bytes SDRAM for VRAM
... snip ...

  and it does boot successfully (well, after i added the touchscreen
from one of my other kits). but clearly there's a build that works.
now all i have to do is figure out how to get the same result with
yocto and the meta-ti layer.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

On 3/27/2013 4:20 PM, Robert P. J. Day wrote:
> On Wed, 27 Mar 2013, Steven Grunza wrote:
>
>> Wow!  You got the SD card?  The kit was supposed to come with a
>> Windows CE and a Linux SD card but I didn't get either.  I was never
>> able to get LogicPD support to send me the image, either.  They just
>> kept pointing the the procedures spread all over the web on how to
>> build the code.
>    just to establish a foundation here, this is the result of booting
> from the SD card that came with the board from logicpd:
>
> =====start=====
> ...
> 218976 Bytes Read from MMC
> Starting OS Bootloader from MMC...
> Starting OS Bootloader...
>
>
> U-Boot 2009.11 (Jan 22 2011 - 01:45:10)
>
> OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
> AM3517EVM Board + LPDDR/NAND
> I2C:   ready
> DRAM:  256 MB
> NAND:  512 MiB
> *** Warning - bad CRC or NAND, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Die ID #40be00010000000001685a2001015021
> Net:   davinci_emac_initialize
> Ethernet PHY: GENERIC @ 0x00
> DaVinci EMAC
> Hit any key to stop autoboot:  0
> mmc1 is available
> reading boot.scr
>
> ** Unable to read "boot.scr" from mmc 0:1 **
> reading uImage
>
> 2308136 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 82000000 ...
>     Image Name:   Arago/2.6.32-psp03.00.01.06.sdk/
>     Image Type:   ARM Linux Kernel Image (uncompressed)
>     Data Size:    2308072 Bytes =  2.2 MB
>     Load Address: 80008000
>     Entry Point:  80008000
>     Verifying Checksum ... OK
>     Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing
> Linux.................................................................................................
> Linux version 2.6.32 (schuyler_2@neo) (gcc version 4.3.3 (Sourcery G++
> Lite 2009q1-203) ) #1 Tue Jan 25 16:18:32 CS1
> CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f
> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
> Machine: OMAP3517/AM3517 EVM
> Memory policy: ECC disabled, Data cache writeback
> AM3517 ES3.1 (l2cache iva sgx neon isp )
> SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
> Reserving 4194304 bytes SDRAM for VRAM
> ... snip ...
>
>    and it does boot successfully (well, after i added the touchscreen
> from one of my other kits). but clearly there's a build that works.
> now all i have to do is figure out how to get the same result with
> yocto and the meta-ti layer.
>
> rday
>
Robert,
   Could you dd the SD card into a compressed image and send it to me?  
I might need to setup some sort of scp drop location if it's too big to 
email.  While I want to be able to build the code, I really need to get 
this robot done in time for the April competition...

Steven G.

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

On 3/20/2013 2:27 PM, Denys Dmytriyenko wrote:
> On Wed, Mar 20, 2013 at 02:18:28PM -0400, Steven Grunza wrote:
>> On 3/20/2013 1:54 PM, Denys Dmytriyenko wrote:
>>> On Wed, Mar 20, 2013 at 01:48:21PM -0400, Steven Grunza wrote:
>>>> On 3/20/2013 11:17 AM, Denys Dmytriyenko wrote:
>>>>> On Wed, Mar 20, 2013 at 10:23:34AM -0400, Steven Grunza wrote:
>>>>>> On 3/19/2013 2:27 PM, Denys Dmytriyenko wrote:
>>>>>>> On Tue, Mar 19, 2013 at 02:08:52PM -0400, Steven Grunza wrote:
>>>>>>>> On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
>>>>>>>>> On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
>>>>>>>>>> Hello,
>>>>>>>>>>    I have a LogicPD Zoom AM3517 experimenters board.  Is this the
>>>>>>>>>> correct list to ask questions about getting Yocto-based software
>>>>>>>>>> running on this board?
>>>>>>>>> Yes, this is one of the correct lists for asking questions about AM3517 board
>>>>>>>>> when used with the Yocto Project. :) As this is the mailing list for meta-ti,
>>>>>>>>> which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
>>>>>>>>> the Yocto Project, and AM3517 is currently one of the supported platforms in
>>>>>>>>> meta-ti.
>>>>>>>>>
>>>>>>>> Wonderful.  Can someone point me to information so that I can build
>>>>>>>> a system using the Yocto project and program an SD card with the
>>>>>>>> necessary files to boot my board into Linux?
>>>>>>>>
>>>>>>>>    With all of the S7 DIP switches in the off position (which the
>>>>>>>> AM3517 Development Kits User Manual indicates is the default boot
>>>>>>> >from NAND) I don't get any output from the serial UART so my guess
>>>>>>>> is that I've hosed the NAND.
>>>>>>>>
>>>>>>>>    For debugging support I have a TI Stellaris LM3S8962 board which
>>>>>>>> has the ability to act as a JTAG debugger to external hardware.  For
>>>>>>>> software I have OpenOCD 0.6.1
>>>>>>> I would assume you already checked this Hardware Setup page:
>>>>>>> http://processors.wiki.ti.com/index.php/GSG:_AM35x_EVM_Hardware_Setup
>>>>>>>
>>>>>>> Then you would need to check the Boot from SD/MMC page:
>>>>>>> http://processors.wiki.ti.com/index.php/AM35x_EVM_Boot_from_SD/MMC_card
>>>>>>>
>>>>>>> As of the software load, you can build a minimal rootfs image (e.g.
>>>>>>> core-image-minimal) with all the BSP components and setup an SD card as
>>>>>>> described above. You'll get the MLO, u-boot, uImage and rootfs as the
>>>>>>> output of the build, that you need to load on to the card.
>>>>>> To what should I have MACHINE set?  Using beagleboard didn't work.
>>>>> There is "am3517-evm" machine in meta-ti:
>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/conf/machine
>>>>>
>>>> What is the proper way to include the above file in my build
>>>> environment or is there a URL describing it that I've missed?
>>> You need to add meta-ti layer to your configuration. It can be as easy as
>>> git-cloning it into your sources location, along with other "meta" layers and
>>> adding it to your bblayers.conf file. You'd need to also add BBMASK to your
>>> local.conf, as described in meta-ti README file. After that you can build for
>>> MACHINE=am3517-evm
>>>
>> I did something wrong or missed a step.  I got:
>>
>> grunzasr@stm32dbg:/home/yocto/poky-danny-8.0/build$ bitbake
>> core-image-sato-sdk
>> Pseudo is not present but is required, building this first before
>> the main build
>> Parsing recipes: 100% |#####################################################################################################|
>> Time: 00:02:17
>> Parsing of 899 .bb files complete (0 cached, 899 parsed). 1205
>> targets, 67 skipped, 7 masked, 0 errors.
>> ERROR: No recipes available for:
>> /home/yocto/poky-danny-8.0/meta-ti/recipes-graphics/mesa/mesa-dri_9.0.2.bbappend
>> ERROR: Command execution failed: Exited with 1
>>
>> I put the meta-ti (via a git clone) into /home/yocto/poky-danny-8.0
> If you are using poky-danny as a base, you need to use "danny" branch of
> meta-ti to match the versions.
>
How can I get a danny branch?

Re: Is this the correct list for AM3517 EVM questions?

[Denys Dmytriyenko]

On Wed, Mar 20, 2013 at 02:48:19PM -0400, Steven Grunza wrote:
> >>I did something wrong or missed a step.  I got:
> >>
> >>grunzasr@stm32dbg:/home/yocto/poky-danny-8.0/build$ bitbake
> >>core-image-sato-sdk
> >>Pseudo is not present but is required, building this first before
> >>the main build
> >>Parsing recipes: 100% |#####################################################################################################|
> >>Time: 00:02:17
> >>Parsing of 899 .bb files complete (0 cached, 899 parsed). 1205
> >>targets, 67 skipped, 7 masked, 0 errors.
> >>ERROR: No recipes available for:
> >>/home/yocto/poky-danny-8.0/meta-ti/recipes-graphics/mesa/mesa-dri_9.0.2.bbappend
> >>ERROR: Command execution failed: Exited with 1
> >>
> >>I put the meta-ti (via a git clone) into /home/yocto/poky-danny-8.0
> >If you are using poky-danny as a base, you need to use "danny" branch of
> >meta-ti to match the versions.
> >
> How can I get a danny branch?

git checkout -b danny origin/danny
man git

-- 
Denys

Re: Is this the correct list for AM3517 EVM questions?

[Steven Grunza]

On 3/19/2013 1:21 PM, Denys Dmytriyenko wrote:
> On Tue, Mar 19, 2013 at 10:18:33AM -0400, Steven Grunza wrote:
>> Hello,
>>    I have a LogicPD Zoom AM3517 experimenters board.  Is this the
>> correct list to ask questions about getting Yocto-based software
>> running on this board?
> Yes, this is one of the correct lists for asking questions about AM3517 board
> when used with the Yocto Project. :) As this is the mailing list for meta-ti,
> which is the official Texas Instruments BSP layer for OpenEmbedded-Core and
> the Yocto Project, and AM3517 is currently one of the supported platforms in
> meta-ti.
>
Wonderful.  Can someone point me to information so that I can build a 
system using the Yocto project and program an SD card with the necessary 
files to boot my board into Linux?

   With all of the S7 DIP switches in the off position (which the AM3517 
Development Kits User Manual indicates is the default boot from NAND) I 
don't get any output from the serial UART so my guess is that I've hosed 
the NAND.