public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dragos Carp <dragos.carp@toptica.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Getting RedBoot[ROM] into the Phytec PhyCORE-MPC555
Date: Wed, 09 Jun 2004 07:49:00 -0000	[thread overview]
Message-ID: <40C6C106.9050700@toptica.com> (raw)
In-Reply-To: <1086724679.40c61a47339c3@engin.mail.umich.edu>

Hi Miguel,

Unfortunately I have no experience with CodeWarrior's flash programmer 
(I use only GNU tools and a custom BDM interface), my Redboot is 
programmed in external flash (dual mapped to address 0x00). During 
development process, because of the inconvenient update, I donÂ’t intend 
to write it in internal flash.

Regarding your .srec load problem, I wonder if the CodeWarrior's flash 
programmer is able to interpret the .srec file, actually this is a human 
readable text file. Normally you should write in the internal flash just 
a binary representation from your .elf file (see powerpc-eabi-objcopy 
“–O binary” option).

If IÂ’ll need to write into the internal flash, my first attempt will be 
to write a small program, which uses PhytecÂ’s supplied routine for 
writing into the internal flash. This program and the binary image, both 
loaded in moduleÂ’s RAM, should do the job.

Best regards,

Dragos

mserrano@engin.umich.edu wrote:

>Hi Dragos and eCos list,
>
>We are currently trying to get RedBoot[ROM] into internal flash using
>CodeWarrior 8.0 flash programmer. We are using Phytec's
>phyCORE-MPC555_BDM_init.cfg as the target initialization file and
>converting the redboot.elf file generated by the configuration tools into
>a Motorolla S-record file (S3) (this is the file that we are actually
>trying to burn into internal flash). Unfortunately this is not working. This is
>what the flash programmer log looks like:
>
>======================================================================
>=== Execute: Program
>=== Timestamp:  Tue Jun  8 15:29:38 2004
>=== Flash Device:         MPC555
>=== Flash Organization:   448Kx8x1
>=== Flash Mem Start Addr: 0x00000000
>=== Flash Mem End Addr:   0x0006FFFF
>======================================================================
>Using restricted address range 0x00000000 to 0x0006FFFF
>
>Using Algorithm: mpc555.elf
>
>Loading Flash Device Driver at: 0x00C00000
>Flash Driver Buffer is at:      0x00C029E0
>Flash Driver Buffer Size is:    0x00003620
>Done
>
>Initialization Command Succeeded
>Programming file C:\Software_stuff\redboot_rom.srec
>
>Programming 0x00010000 bytes of Target Memory at 0x00000000
>Flash Programmer:  Flash driver reports the following error(s):  Chip
>reported error during program
>
>Did you use CodeWarrior's flash programmer? Does anyone know of a different
>method of programming into internal flash?
>
>Thanks,
>Miguel J. Vega
>FEGI C&DH Team
>University of Michigan
>
>
>
>
>  
>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2004-06-09  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 19:58 mserrano
2004-06-09  7:49 ` Dragos Carp [this message]

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=40C6C106.9050700@toptica.com \
    --to=dragos.carp@toptica.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).