public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Evgeniy Dushistov <dushistov@mail.ru>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Development List <ecos-devel@ecos.sourceware.org>
Subject: Re: Getting Atmel AT91SAM9 into eCos
Date: Thu, 17 Mar 2011 14:53:00 -0000	[thread overview]
Message-ID: <20110317145342.GA11311@maclin> (raw)
In-Reply-To: <4D80D629.40307@dallaway.org.uk>

On Wed, Mar 16, 2011 at 03:24:25PM +0000, John Dallaway wrote:
> I am looking to get QEMU working for review of your AT91SAM9263 eCos
> contribution.
> 
> Evgeniy Dushistov wrote:
> 
> >>> Actually, I and Filip Navara implemented AT91SAM7X and at91sam9263
> >>> support for qemu, one of the most recent version can be found here:
> >>> git://github.com/Dushistov/qemu_at91sam9263.git
> >>> It can run linux, freertos, ecos.
> 
> I have tried running up an eCos test built for target "at91sam7xek" with
> "kernel" template (ROM startup) using QEMU built from your git sources:
> 

There is little misconfiguration, qemu for sam7x have no support nor flash,
ecos for 7x have no support ram startup. I never try ecos for sam7,
but this is not big problem.

I fixed this issue (below path to repo and branch where is fix). 
So little instruction for anybody who want try qemu with
at91 support:

$git clone --branch at91sam_support_for_merge git://github.com/Dushistov/qemu_at91sam9263.git qemu_at91sam
$cd qemu_at91sam
$./configure --target-list="arm-softmmu arm-linux-user armeb-linux-user"
$make

build at91sam7xek kernel and tests,
create binary file from some executable, for example:
$arm-eabi-objcopy -O binary bin_sem0 bin_sem0.bin

create flash image:

$dd if=/dev/zero of=/tmp/flash.bin count=128 bs=1024
$dd if=./bin_sem0.bin of=/tmp/flash.bin conv=notrunc

and run it:
$./arm-softmmu/qemu-system-arm   -serial tcp::4445,server  -M at91pes
-pflash /tmp/flash.bin &

connect to serial port:
$telnet localhost 4445
and you will see:
PASS:<Binary Semaphore 0 OK>
EXIT:<done>

-- 
/Evgeniy

       reply	other threads:[~2011-03-17 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1266877649.3024.105.camel@localhost.localdomain>
     [not found] ` <4B839F37.50904@dallaway.org.uk>
     [not found]   ` <20100223100104.GA15310@rain>
     [not found]     ` <4B840808.1090208@mlbassoc.com>
     [not found]       ` <20100223175227.GA16660@rain>
     [not found]         ` <4D80D629.40307@dallaway.org.uk>
2011-03-17 14:53           ` Evgeniy Dushistov [this message]
2011-03-17 15:39             ` John Dallaway

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=20110317145342.GA11311@maclin \
    --to=dushistov@mail.ru \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).