This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: problem getting gdb talking to Cirrus Logic 7312 dev board


I've followed the section, rebuilding redboot for my 7312 eval board.
This is in the redboot users guide chapter 3.

so go get the latest ecosconfig program and do the following in a new
directory:
NOTE: you will need to set up the ECOS_REPOSITORY environment variable to
point to where the ecos/redboot source tree is.

1) ecosconfig new edb7xxx redboot
2) ecosconfig import <path to ecos
source>/packages/hal/arm/edb7xxx/current/misc/edb7312_redboot_ROM.ecm
3) ecosconfig tree
4) make

Then in the install/bin directory, you will have a redboot.bin file.
Download this to the eval card with the utility from Cirrus.

Also, you must build this with a gcc cross compiler for arm-elf.

Good Luck,
Adam

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Yin Bao
Sent: Tuesday, November 05, 2002 3:33 PM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] problem getting gdb talking to Cirrus Logic 7312 dev
board



Got the following from gdb:

(gdb) target remote COM1
Remote debugging using COM1
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Couldn't establish connection to remote target
Malformed response to offset query, timeout

I am following the instructions from 'Getting started
with ecos' which has instructions for Cirrus Logic 7212.
I built the gdb_module.img and downloaded onto the
board though I did get a conflict which I chose
"continue" with all proposed solutions (bad idea?)

Then, I tried to download the redboot_ROMRAM.bin that came
with the package onto the board and it came up and crashed
shortly (complained about eth interface at startup which
mac address not set, probably not ecos problem). Also tried
the redboot_RAM version and got the same error as above.

Which way should I go? Is gdb_module all I need or do I need
redboot? Eventually I will need to debug my own hardware
instead of CirrusLogic dev board (but the same processor),
do I need redboot at that time?

I have ecos of 10-28-2002 snapshot from ecoscentric,
gdb 5.2.1, download.exe is provided by Cirrus Logic
as part of 7312 dev. kit/board. Currently all things
running from Windows.

Thanks in advance for any help!

Yin



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





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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]