From: Wolfram Kattanek <wolfram.kattanek@imms.de>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Problems with CEB-v850/SA1
Date: Thu, 08 Feb 2001 03:16:00 -0000 [thread overview]
Message-ID: <981630950.3a827fe6412de@imp.imms.de> (raw)
In-Reply-To: <3A6CC0A1.2A7CBDF6@redhat.com>
Jonathan Larmour <jlarmour@redhat.com>:
> As for your other problem, I have fixed that in local sources as it
> happens, but haven't checked it in yet. I've attached a known good GDB stub
> ROM. Use v850-elf-objcopy to copy it from ELF to other formats for
> programming (bin, srec).
>
> You will also need to make sure the attached v850.hex file is programmed
> into your chip internal flash. It may already be... I confess I'm not clear
> on what the V850s on Cosmo boards ships with.
Jonathan,
not long ago you helped us with our problems regarding the CEB-v850/SA1 board.
You sent a "known good GDB stub" file and mentioned that you eventually will
check in the fixed local sources. Did you do that already? Or can you give us
a hint which sources we have to use to build a "good GDB stub" for our own?
We need a "good" starting point for our porting activities.
What is the function of v850.hex file? Because of some HW problems we couldn't
program it yet. We're trying to port eCos to another V850/SA1 board (startWARE
from NEC) and thats why every information is very welcome!
Wolfram
--
Wolfram 'L.A.' Kattanek Institut fuer Mikroelektronik- und
Email: LA@imms.de Mechatronik-Systeme (IMMS) gGmbH
Tel: +49 3677 / 6783-55 Langewiesener Str. 22
Fax: +49 3677 / 6783-38 98693 Ilmenau / Germany
-------------------------------------------------
This mail sent through IMP: imp.imms.de
prev parent reply other threads:[~2001-02-08 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 14:41 Wolfram Kattanek
2001-01-22 15:22 ` Jonathan Larmour
2001-01-26 8:12 ` Wolfram Kattanek
2001-02-08 3:16 ` Wolfram Kattanek [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=981630950.3a827fe6412de@imp.imms.de \
--to=wolfram.kattanek@imms.de \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jlarmour@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).