EmbeddedRelated.com
Forums
Memfault Beyond the Launch

Not Flash ID

Started by kapil_chittewan August 16, 2006
Hello all,

We have developed rabbit based module at our place. We have carried
out some diagnostic test and found ok. During cold boot mode, when I
compile 'file.c' program it will stop loading at 128/10535 and give a
message "While sending User program: Target communication error". We
have also load a .bin file trough the Rabbit Field Utility(RFU.exe).
In that case it will give a message "Flash parameters for flash ID
return from pilot bios were not found in the flash initialization
file"

I think it is not getting the SysIDBlock structure where the flash
ID is present.
please tell me how to solve this problem

Thanks and Regards

Kapil C.
Your RFU is old and doesn't know about the newer flash chips.
-Pete

-----Original Message-----
From: r... [mailto:r...]
On Behalf Of kapil_chittewan
Sent: Wednesday, August 16, 2006 9:26 AM
To: r...
Subject: [rabbit-semi] Not Flash ID
Hello all,

We have developed rabbit based module at our place. We have carried
out some diagnostic test and found ok. During cold boot mode, when I
compile 'file.c' program it will stop loading at 128/10535 and give a
message "While sending User program: Target communication error". We
have also load a .bin file trough the Rabbit Field Utility(RFU.exe).
In that case it will give a message "Flash parameters for flash ID
return from pilot bios were not found in the flash initialization
file"

I think it is not getting the SysIDBlock structure where the flash
ID is present.
please tell me how to solve this problem

Thanks and Regards

Kapil C.
hi Pete,

well we have Dynamic C 9.21 version and the RFU comes with this. if it is old then from where do i get the new version of RFU. But please tell me that whether SysIDBlock should present there or not

waiting your reply
Thanks
Kapil C

"Fournier, Pete" wrote:
Your RFU is old and doesn't know about the newer flash chips.
-Pete

-----Original Message-----
From: r... [mailto:r...]
On Behalf Of kapil_chittewan
Sent: Wednesday, August 16, 2006 9:26 AM
To: r...
Subject: [rabbit-semi] Not Flash ID

Hello all,

We have developed rabbit based module at our place. We have carried
out some diagnostic test and found ok. During cold boot mode, when I
compile 'file.c' program it will stop loading at 128/10535 and give a
message "While sending User program: Target communication error". We
have also load a .bin file trough the Rabbit Field Utility(RFU.exe).
In that case it will give a message "Flash parameters for flash ID
return from pilot bios were not found in the flash initialization
file"

I think it is not getting the SysIDBlock structure where the flash
ID is present.
please tell me how to solve this problem

Thanks and Regards

Kapil C.

Yahoo! Groups Links

---------------------------------
Here's a new way to find what you're looking for - Yahoo! Answers
Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW
I don't use a SysIDBlock. Check the files that came with the RFU and
see if the prom you are using is listed. If it isn't you have 2
choices, change to a listed prom or use the documentation in the RFU
files to add a new prom description.

-Pete

-----Original Message-----
From: r...
[mailto:r...] On Behalf Of Kapil Chittewan
Sent: Thursday, August 17, 2006 1:13 AM
To: r...
Subject: RE: [rabbit-semi] Not Flash ID

hi Pete,

well we have Dynamic C 9.21 version and the RFU comes with this.
if it is old then from where do i get the new version of RFU. But please
tell me that whether SysIDBlock should present there or not

waiting your reply
Thanks
Kapil C

"Fournier, Pete" wrote:

Your RFU is old and doesn't know about the newer flash
chips.
-Pete

-----Original Message-----
From: r...

[mailto:r...
]
On Behalf Of kapil_chittewan
Sent: Wednesday, August 16, 2006 9:26 AM
To: r...

Subject: [rabbit-semi] Not Flash ID

Hello all,

We have developed rabbit based module at our place. We
have carried
out some diagnostic test and found ok. During cold boot
mode, when I
compile 'file.c' program it will stop loading at
128/10535 and give a
message "While sending User program: Target
communication error". We
have also load a .bin file trough the Rabbit Field
Utility(RFU.exe).
In that case it will give a message "Flash parameters
for flash ID
return from pilot bios were not found in the flash
initialization
file"

I think it is not getting the SysIDBlock structure where
the flash
ID is present.
please tell me how to solve this problem

Thanks and Regards

Kapil C.

Yahoo! Groups Links

________________________________

Here's a new way to find what you're looking for - Yahoo!
Answers


Send FREE SMS to your friend's mobile from Yahoo! Messenger
Version 8. Get it NOW
hi,

i checked file at 'C:\DCRABBIT_9.21\Flash.ini' and prom is listed
over there.
As per the documents it says that the BIOS will read the System ID
block during startup.
If the BIOS does not find an ID block, it
sets all fields to zero in the data structure SysIDBlock where the
flash ID is present.

will BIOS detect the flash even though there is no SysIDBlock
structure?

waiting your reply
thanks
Kapil C.

--- In r..., "Fournier, Pete"
wrote:
>
> I don't use a SysIDBlock. Check the files that came with the RFU
and
> see if the prom you are using is listed. If it isn't you have 2
> choices, change to a listed prom or use the documentation in the RFU
> files to add a new prom description.
>
> -Pete
>
> -----Original Message-----
> From: r...
> [mailto:r...] On Behalf Of Kapil Chittewan
> Sent: Thursday, August 17, 2006 1:13 AM
> To: r...
> Subject: RE: [rabbit-semi] Not Flash ID
>
>
> hi Pete,
>
> well we have Dynamic C 9.21 version and the RFU comes with
this.
> if it is old then from where do i get the new version of RFU. But
please
> tell me that whether SysIDBlock should present there or not
>
> waiting your reply
> Thanks
> Kapil C
>
> "Fournier, Pete" wrote:
>
> Your RFU is old and doesn't know about the newer flash
> chips.
> -Pete
>
> -----Original Message-----
> From: r...
>
> [mailto:r...
> ]
> On Behalf Of kapil_chittewan
> Sent: Wednesday, August 16, 2006 9:26 AM
> To: r...
>
> Subject: [rabbit-semi] Not Flash ID
>
> Hello all,
>
> We have developed rabbit based module at our place. We
> have carried
> out some diagnostic test and found ok. During cold
boot
> mode, when I
> compile 'file.c' program it will stop loading at
> 128/10535 and give a
> message "While sending User program: Target
> communication error". We
> have also load a .bin file trough the Rabbit Field
> Utility(RFU.exe).
> In that case it will give a message "Flash parameters
> for flash ID
> return from pilot bios were not found in the flash
> initialization
> file"
>
> I think it is not getting the SysIDBlock structure
where
> the flash
> ID is present.
> please tell me how to solve this problem
>
> Thanks and Regards
>
> Kapil C.
>
>
I've developed several R3K boards, never tested the RFU although.
I just dont think it will work without an ID Block, but dont know for
sure.

What we've done:
- Written a very short bootloader (the triplet system thing) which is
loaded in RAM. It sets up the MMU and includes a compact Flash write
routine. Not the big fancy Flach write functions of DC. If you check
the datasheet of your Flash IC, you'll notice writing to a Flash is
not that complicated.
- Then the bootloader starts, reads the data from the Serial Port and
stores that in the Flash

I cant share the code, and anyhow it's rather specific for our
hardware. But this is the way you should go in a production environment.

If you're just prototyping, you can manage in DC. There is a sample
program available (in this group I think) to write the ID Block.
Follow the instructions, make the changes for your product (ID, Flash
type, etc...), and load the program in RAM. It will run fine, even
without an ID Block. Once the ID Block is written, you can run your
own programs.

Note, that you will need to adapt BOARDTYPES.LIB if your hardware is
not an exact copy of an RCM hardware module. If you want some info on
how we've implemented it, you can download our product manual at
www.x-graph.be. It has a section on installation and BOARDTYPES/BIOS
changes.

Rudi
www.x-graph.be the next generation Rabbit SBC with (Color TFT) LCD

--- In r..., "kapil_chittewan"
wrote:
>
> hi,
>
> i checked file at 'C:\DCRABBIT_9.21\Flash.ini' and prom is listed
> over there.
> As per the documents it says that the BIOS will read the System ID
> block during startup.
> If the BIOS does not find an ID block, it
> sets all fields to zero in the data structure SysIDBlock where the
> flash ID is present.
>
> will BIOS detect the flash even though there is no SysIDBlock
> structure?
>
> waiting your reply
> thanks
> Kapil C.
>
> --- In r..., "Fournier, Pete"
> wrote:
> >
> > I don't use a SysIDBlock. Check the files that came with the RFU
> and
> > see if the prom you are using is listed. If it isn't you have 2
> > choices, change to a listed prom or use the documentation in the RFU
> > files to add a new prom description.
> >
> > -Pete
> >
> > -----Original Message-----
> > From: r...
> > [mailto:r...] On Behalf Of Kapil Chittewan
> > Sent: Thursday, August 17, 2006 1:13 AM
> > To: r...
> > Subject: RE: [rabbit-semi] Not Flash ID
> >
> >
> > hi Pete,
> >
> > well we have Dynamic C 9.21 version and the RFU comes with
> this.
> > if it is old then from where do i get the new version of RFU. But
> please
> > tell me that whether SysIDBlock should present there or not
> >
> > waiting your reply
> > Thanks
> > Kapil C
> >
> >
> >
> > "Fournier, Pete" wrote:
> >
> > Your RFU is old and doesn't know about the newer flash
> > chips.
> > -Pete
> >
> > -----Original Message-----
> > From: r...
> >
> > [mailto:r...
> > ]
> > On Behalf Of kapil_chittewan
> > Sent: Wednesday, August 16, 2006 9:26 AM
> > To: r...
> >
> > Subject: [rabbit-semi] Not Flash ID
> >
> > Hello all,
> >
> > We have developed rabbit based module at our place. We
> > have carried
> > out some diagnostic test and found ok. During cold
> boot
> > mode, when I
> > compile 'file.c' program it will stop loading at
> > 128/10535 and give a
> > message "While sending User program: Target
> > communication error". We
> > have also load a .bin file trough the Rabbit Field
> > Utility(RFU.exe).
> > In that case it will give a message "Flash parameters
> > for flash ID
> > return from pilot bios were not found in the flash
> > initialization
> > file"
> >
> > I think it is not getting the SysIDBlock structure
> where
> > the flash
> > ID is present.
> > please tell me how to solve this problem
> >
> > Thanks and Regards
> >
> > Kapil C.
> >
> >
Kapil,

Check this: Open the RFU, go to SETUP and then FILE LOCATIONS. Make
SURE the ColdLoader, PilotBios and FlashTable are all coming from the
same place and are the latest versions.

I have to admit that I never went past DC version 8.61, but I would
surprised if you the ID Block because Rabbit Semi has code to allow you
to write an ID block and it loads thru the RFU!. I have found the ID
Block is useful when you run the compiler (or your code) to take
advantage of the info during compile time while the programming cable is
attached to a live unit.

You said the error message you got was:
"Flash parameters for flash ID return from pilot bios were not found in
the flash initialization file"
This does not seem to be indicating an ID Bock problem.

-Pete

-----Original Message-----
From: r... [mailto:r...]
On Behalf Of kapil_chittewan
Sent: Friday, August 18, 2006 12:03 AM
To: r...
Subject: [rabbit-semi] Re: Not Flash ID
hi,

i checked file at 'C:\DCRABBIT_9.21\Flash.ini' and prom is listed
over there.
As per the documents it says that the BIOS will read the System ID
block during startup.
If the BIOS does not find an ID block, it
sets all fields to zero in the data structure SysIDBlock where the
flash ID is present.

will BIOS detect the flash even though there is no SysIDBlock
structure?

waiting your reply
thanks
Kapil C.

--- In r..., "Fournier, Pete"
wrote:
>
> I don't use a SysIDBlock. Check the files that came with the RFU
and
> see if the prom you are using is listed. If it isn't you have 2
> choices, change to a listed prom or use the documentation in the RFU
> files to add a new prom description.
>
> -Pete
>
> -----Original Message-----
> From: r...
> [mailto:r...] On Behalf Of Kapil Chittewan
> Sent: Thursday, August 17, 2006 1:13 AM
> To: r...
> Subject: RE: [rabbit-semi] Not Flash ID
>
>
> hi Pete,
>
> well we have Dynamic C 9.21 version and the RFU comes with
this.
> if it is old then from where do i get the new version of RFU. But
please
> tell me that whether SysIDBlock should present there or not
>
> waiting your reply
> Thanks
> Kapil C
>
> "Fournier, Pete" wrote:
>
> Your RFU is old and doesn't know about the newer flash
chips.
> -Pete
>
> -----Original Message-----
> From: r...
>
> [mailto:r...
> ]
> On Behalf Of kapil_chittewan
> Sent: Wednesday, August 16, 2006 9:26 AM
> To: r...
>
> Subject: [rabbit-semi] Not Flash ID
>
> Hello all,
>
> We have developed rabbit based module at our place. We
> have carried
> out some diagnostic test and found ok. During cold
boot
> mode, when I
> compile 'file.c' program it will stop loading at
> 128/10535 and give a
> message "While sending User program: Target
> communication error". We
> have also load a .bin file trough the Rabbit Field
Utility(RFU.exe).
> In that case it will give a message "Flash parameters
> for flash ID
> return from pilot bios were not found in the flash
> initialization
> file"
>
> I think it is not getting the SysIDBlock structure
where
> the flash
> ID is present.
> please tell me how to solve this problem
>
> Thanks and Regards
>
> Kapil C.
>
>
Hi Kapil,

From ur previous posts i noticed that you are facing an
error "While sending user program: Target communication error" .
Were you able to resove this issue ? Coz I am using RABBIT4000 (with
My own customised board) i too face the same error. Its loading to
RAM succesfully, but while loading into FLASH i notice the above
mentioned error.

If you are successfull in resolving the error plz do help me out.

Waiting for your quick response.

Thanks & Regards,
Sathya

--- In r..., "Fournier, Pete"
wrote:
>
> Kapil,
>
> Check this: Open the RFU, go to SETUP and then FILE LOCATIONS.
Make
> SURE the ColdLoader, PilotBios and FlashTable are all coming from
the
> same place and are the latest versions.
>
> I have to admit that I never went past DC version 8.61, but I would
> surprised if you the ID Block because Rabbit Semi has code to
allow you
> to write an ID block and it loads thru the RFU!. I have found the
ID
> Block is useful when you run the compiler (or your code) to take
> advantage of the info during compile time while the programming
cable is
> attached to a live unit.
>
> You said the error message you got was:
> "Flash parameters for flash ID return from pilot bios were not
found in
> the flash initialization file"
> This does not seem to be indicating an ID Bock problem.
>
> -Pete
>
> -----Original Message-----
> From: r... [mailto:rabbit-
s...]
> On Behalf Of kapil_chittewan
> Sent: Friday, August 18, 2006 12:03 AM
> To: r...
> Subject: [rabbit-semi] Re: Not Flash ID
> hi,
>
> i checked file at 'C:\DCRABBIT_9.21\Flash.ini' and prom is listed
> over there.
> As per the documents it says that the BIOS will read the System ID
> block during startup.
> If the BIOS does not find an ID block, it
> sets all fields to zero in the data structure SysIDBlock where the
> flash ID is present.
>
> will BIOS detect the flash even though there is no SysIDBlock
> structure?
>
> waiting your reply
> thanks
> Kapil C.
>
> --- In r..., "Fournier, Pete"
> wrote:
> >
> > I don't use a SysIDBlock. Check the files that came with the RFU
> and
> > see if the prom you are using is listed. If it isn't you have 2
> > choices, change to a listed prom or use the documentation in the
RFU
> > files to add a new prom description.
> >
> > -Pete
> >
> > -----Original Message-----
> > From: r...
> > [mailto:r...] On Behalf Of Kapil Chittewan
> > Sent: Thursday, August 17, 2006 1:13 AM
> > To: r...
> > Subject: RE: [rabbit-semi] Not Flash ID
> >
> >
> > hi Pete,
> >
> > well we have Dynamic C 9.21 version and the RFU comes with
> this.
> > if it is old then from where do i get the new version of RFU. But
> please
> > tell me that whether SysIDBlock should present there or not
> >
> > waiting your reply
> > Thanks
> > Kapil C
> >
> >
> >
> > "Fournier, Pete" wrote:
> >
> > Your RFU is old and doesn't know about the newer
flash
> chips.
> > -Pete
> >
> > -----Original Message-----
> > From: r...
> >
> > [mailto:r...
> > ]
> > On Behalf Of kapil_chittewan
> > Sent: Wednesday, August 16, 2006 9:26 AM
> > To: r...
> >
> > Subject: [rabbit-semi] Not Flash ID
> >
> > Hello all,
> >
> > We have developed rabbit based module at our place.
We
> > have carried
> > out some diagnostic test and found ok. During cold
> boot
> > mode, when I
> > compile 'file.c' program it will stop loading at
> > 128/10535 and give a
> > message "While sending User program: Target
> > communication error". We
> > have also load a .bin file trough the Rabbit Field
> Utility(RFU.exe).
> > In that case it will give a message "Flash parameters
> > for flash ID
> > return from pilot bios were not found in the flash
> > initialization
> > file"
> >
> > I think it is not getting the SysIDBlock structure
> where
> > the flash
> > ID is present.
> > please tell me how to solve this problem
> >
> > Thanks and Regards
> >
> > Kapil C.
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> > ________________________________
> >
> > Here's a new way to find what you're looking for - Yahoo!
> Answers
>
/
> >
> >
> > Send FREE SMS to your friend's mobile from Yahoo! Messenger
> Version
> > 8. Get it NOW
>
o
> m>
> >
>
> Yahoo! Groups Links
>

Memfault Beyond the Launch