[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Problem with Developer Board



Hi.
It seems to me that you are not setting all necessary registers before
making the flash program, e.g. initialisation of RAM etc.
Try to start flash programming using the command below:

#!/bin/sh
etrax100boot \
--setreg b0000000 000095f8 \
--setreg b0000004 00000104 \
--setreg b000000c 1a200040 \
--setreg b0000008 00005611 \
--setreg b0000030 00001df0 \
--setreg b0000038 00001ef3 \
--file fimage c0004000 \
--flash c0014000 10000 1f0000 
--jump 0

Brgds
/Magnus

> -----Original Message-----
> From: B.Ashraf@xxxxxxx.uk">mailto:B.Ashraf@xxxxxxx.uk]
> Sent: den 15 maj 2003 12:21
> To: orjanf@xxxxxxx.com
> Subject: Re: Problem with Developer Board
> 
> 
> Dear Orjan,
> 
> Here is what i did. Although i still cant get access to the 
> board through its IP
> address or through com port.
> 
> 1. started SERMON
> 2. Put the board in boot mode
> 3. flashit
> 4. the following messages came
> 
> SET_REGISTER
> 0XB0000038
> 0X00001EF3
> PACKET_INFO
> 0XC0004000
> 0X00200018
> checksum of file is 0x00000010
> FLASH
> 0XC0014000
> 0X00010000
> 0X001F0000
> CFI dev 0x800000000
> NO 1x CFI at 0X84000000
> NO Single x16 at 0X84000000
> No Interleaved x16 at 0X84000000
> 0X80010000: Erasing 0x001F0000 bytes....done, verifying ...OK
> 0x80010000: Writing 0x001F0000 bytes....vrified
> JUMP
> 0x00000000
> 
> 5. During the process of writing these messages the orange 
> LED remained On
> continuously
> 6. After these messages were written the orange LED has 
> started blinking
> continuously
> 
> Any suggestions
> bilal
> 
> 
> Quoting Orjan Friberg <orjan.friberg@xxxxxxx.com>:
> 
> > B.Ashraf@xxxxxxx.uk wrote:
> > > Dear Dan,
> > > I tried ktest as well as flashit but to no use. The messages are 
> > > 
> > > *size is 2097176 0x00200018
> > > using internal boot loader:DBG2 - Debug on ser2
> > > starting boot.....
> > > we're doing a flash write, this may take up to a few minutes....
> > > booting device with random id 00005235
> > > nothing more to read. Read: 2097176/2097176
> > > All written
> > > Done.
> > > 
> > > Still I cant connect to the board even through hyperterm.
> > 
> > Connect to the serial debug port (with sermon, which is 
> included with 
> > the development kit, or hyperterm) *before* you do the 
> ktest, and you 
> > will be able to catch the boot log from the board.  If the 
> board boots
> > 
> > at all, the boot log could give a good indication as to 
> what's wrong.
> > 
> > -- 
> > Orjan Friberg
> > Axis Communications
> > 
> > 
> > 
>