From: Denys Dmytriyenko <denys@ti.com>
To: Troy Benjegerdes <hozer@hozed.org>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: regression tests for am3517-evm machine?
Date: Wed, 27 Jan 2016 17:55:29 -0500 [thread overview]
Message-ID: <20160127225529.GC11314@edge> (raw)
In-Reply-To: <20160127221203.GE2584@nl.grid.coop>
On Wed, Jan 27, 2016 at 04:12:03PM -0600, Troy Benjegerdes wrote:
> > > So the first problem seems to be that the 'u-boot' target produces
> > > a build from the 2014.07 version, which does not seem to have any
> > > environment or other setup to load a device tree.
> > >
> > > Is there some patch floating around somewhere that updates the
> > > default u-boot environment to work better with new kernels, or do
> > > I need try and merge something in from the beaglebone
> >
> > Can you try u-boot-ti-staging instead?
>
> This is from 'pokey' ( yocto-2.0-121-g2fb7ee2 ),
> with meta-ti: ( v2012.05-yocto1.2-938-gd397744 )
Strange mix of branches - 2012 was almost 4 years ago... :)
I'd recommend using "fido" branch in all layers, as most tested at the moment.
Still no guarantees about am3517, as that platform hasn't been officially
tested for quite some time.
> U-Boot 2015.07 (Jan 27 2016 - 15:32:32 -0600)
> ...
> AM3517_EVM # printenv
> baudrate=115200
> bootcmd=mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if run loaduimai
> bootdelay=10
> bootfile=uImage
> bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
> console=ttyO2,115200n8
> dieid#=3f42000100000000015da3960e012002
> ethact=DaVinci-EMAC
> loadaddr=0x82000000
> loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr
> loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
> mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootwait
> 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
>
>
>
>
>
> --
> ----------------------------------------------------------------------------
> Troy Benjegerdes 'da hozer' hozer@hozed.org
> 7 elements earth::water::air::fire::mind::spirit::soul grid.coop
>
> Never pick a fight with someone who buys ink by the barrel,
> nor try buy a hacker who makes money by the megahash
>
next prev parent reply other threads:[~2016-01-27 22:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 6:36 regression tests for am3517-evm machine? Troy Benjegerdes
2016-01-18 16:46 ` Denys Dmytriyenko
2016-01-18 20:05 ` Troy Benjegerdes
2016-01-19 18:48 ` Troy Benjegerdes
2016-01-19 19:08 ` Denys Dmytriyenko
2016-01-21 1:58 ` Troy Benjegerdes
2016-01-21 20:48 ` Denys Dmytriyenko
2016-01-21 22:03 ` Robert Nelson
2016-01-21 22:07 ` Denys Dmytriyenko
2016-01-27 21:56 ` Troy Benjegerdes
2016-01-27 22:03 ` Denys Dmytriyenko
2016-01-27 22:12 ` Troy Benjegerdes
2016-01-27 22:55 ` Denys Dmytriyenko [this message]
2016-01-28 4:52 ` Troy Benjegerdes
2016-01-28 16:13 ` Denys Dmytriyenko
2016-01-28 16:33 ` Troy Benjegerdes
2016-01-29 0:09 ` Denys Dmytriyenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160127225529.GC11314@edge \
--to=denys@ti.com \
--cc=hozer@hozed.org \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.