From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Pierre Habraken <Pierre.Habraken@imag.fr>
Cc: Mark Salter <msalter@redhat.com>,
jifl@ecoscentric.com, gary.thomas@mind.be, qqi@theworld.com,
gdb@sources.redhat.com, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Can't connect to remote Evaluator 7T
Date: Thu, 20 Feb 2003 14:38:00 -0000 [thread overview]
Message-ID: <20030220143827.GN11159@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3E54E606.D1FDC422@imag.fr>
> Loading section .text, size 0x3bec lma 0x8000
I think you have used the wrong startup type.
The ROM startup uses:
SECTIONS
{
SECTIONS_BEGIN
CYG_LABEL_DEFN(__reserved_bootmon) = 0x1800000; . = CYG_LABEL_DEFN(__reserved_bootmon) + 0x
20000;
SECTION_rom_vectors (rom, ALIGN (0x8), LMA_EQ_VMA)
SECTION_text (rom, ALIGN (0x1), LMA_EQ_VMA)
SECTION_fini (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata1 (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixup (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_gcc_except_table (rom, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
SECTION_data (ram, 0x8000, FOLLOWING (.gcc_except_table))
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
SECTIONS_END
}
You see that the data section goes at address 0x8000. Im assuming you
have a ROM redboot. So its data section is at the same address you are
downloading your application.
The RAM startup code uses this layout:
SECTIONS
{
SECTIONS_BEGIN
SECTION_fixed_vectors (ram, 0x20, LMA_EQ_VMA)
SECTION_rom_vectors (ram, 0x10000, LMA_EQ_VMA)
SECTION_text (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fini (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_rodata1 (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_fixup (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_gcc_except_table (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_data (ram, ALIGN (0x4), LMA_EQ_VMA)
SECTION_bss (ram, ALIGN (0x4), LMA_EQ_VMA)
CYG_LABEL_DEFN(__heap1) = ALIGN (0x8);
SECTIONS_END
}
Notice that rom_vectors section goes at 0x10000, and everythig else
follows that.
Make sure your build is a RAM build. You may need to delete your work
tree and start again.
Andrew
next prev parent reply other threads:[~2003-02-20 14:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 14:59 Pierre Habraken
2003-02-19 15:30 ` [ECOS] " Jonathan Larmour
2003-02-19 15:59 ` Pierre Habraken
2003-02-19 16:32 ` Jonathan Larmour
2003-02-19 17:14 ` Mark Salter
2003-02-19 17:35 ` Quality Quorum
2003-02-19 17:41 ` Mark Salter
2003-02-19 17:47 ` Gary D. Thomas
2003-02-19 17:59 ` Jonathan Larmour
2003-02-19 19:22 ` Mark Salter
2003-02-20 14:27 ` Pierre Habraken
2003-02-20 14:33 ` Gary D. Thomas
2003-02-20 14:59 ` Pierre Habraken
2003-02-21 8:06 ` Pierre Habraken
2003-02-21 15:14 ` Gary D. Thomas
2003-02-20 14:35 ` Mark Salter
2003-02-20 14:38 ` Andrew Lunn [this message]
2003-02-19 16:44 ` Mark Salter
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=20030220143827.GN11159@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=Pierre.Habraken@imag.fr \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary.thomas@mind.be \
--cc=gdb@sources.redhat.com \
--cc=jifl@ecoscentric.com \
--cc=msalter@redhat.com \
--cc=qqi@theworld.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