RE: [ECOS] GDB stub's checksum

["Edward,Yan-Chi,Lin" <yanchi at oak dot com dot tw>]

Jifl

We have solved the problem. 

What we do is :
1. uuencode the gdb_module.bin to text file
2. Download the image under boot prompt
3. Flashwrite the image to the right position.

Then there isn't error when the eCos is plugged in.

Edward, Yan-Chi, Lin
Senior Software Engineer
Oak Technology Inc. Taiwan


-----Original Message-----
From: jlarmour@redhat.com [mailto:jlarmour@redhat.com]On Behalf Of Jonathan Larmour
Sent: Tuesday, November 07, 2000 3:33 AM
To: Edward,Yan-Chi,Lin
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GDB stub's checksum


"Edward,Yan-Chi,Lin" wrote:
> 
> We are doing a port to evaluator-7T board right now.
> The gdb stub has been built and write to the flash on evaluator-7T like this:
> 
> Boot: rommodules
> Header   Base     Limit
> 018052d8 01800000 0180539c BootStrapLoader v1.0 May 24 2000 14:36:26
> 0180727c 01807000 018072d4 ProductionTest  v1.0 May 24 2000 10:47:26
> 0181a570 01810000 0181a5b8 Angel           1.31.1 (20 Mar 2000)
> 01822d18 01820000 01822d60 Forth interpreter module v1.0
> 01834874 01830000 01834c24 eCos            1.3   (Nov  6 2000) GDB stubs
> 
> But when i type "plugin  eCos" , i got an error message saying
> "Bad checksum 02000000"
> 
> Please give us some suggestions

At a guess, Angel probably expects images to contain their own checksums,
probably at the end. You would need to find out what Angel's requirements
are, i.e. what algorithm is used, where it should go etc.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault