EmbeddedRelated.com
Forums
Memfault Beyond the Launch

No ID Block?

Started by flanderso11 January 20, 2012
Hi

When debugging my project on my RCM6760 and compiling my modified code I got an unexpected message:

line 19 : WARNING SYSCONFIG.LIB : _DC_CLK_DBL_ should always be defined, but was not defined:
line 20 : WARNING SYSCONFIG.LIB : Defined _DC_CLK_DBL_ to 0 (disabled clock doubler recommendation).
line 27 : ERROR BOARDTYPES.LIB : No ID Block found on the target board.
line 28 : ERROR BOARDTYPES.LIB : Please contact Rabbit Technical Support at http://www.digi.com/support for assistance.

Even sample code like pong.c generated the same error message. Since the error seemed board related I switched to my RCM5600W and no errors occured at all.

I understand that the ID Block on the RCM6760 has been corrupted but I don't know how to fix it. From similiar threads I have learned that I need a IDBlock.c or something that clears the ID block.

Is there anyone who have encountered this problem before and have a solution or tip for me?

BR,
Anders

I corrupted my userID block on a RCM6700 i contacted digi and they gave me
a program to rewrite the user id block
ive put it on my dropbox
http://dl.dropbox.com/u/44413828/WriteIdBlock_1064.zip in the examples it
says its for RCM67XX so i presume it will work on your 6760. Had to use
the rabbit field utility with no board verification to upload it to the
board

Good Luck

Phil
On 20 January 2012 13:09, flanderso11
wrote:

> **
>
> Hi
>
> When debugging my project on my RCM6760 and compiling my modified code I
> got an unexpected message:
>
> line 19 : WARNING SYSCONFIG.LIB : _DC_CLK_DBL_ should always be defined,
> but was not defined:
> line 20 : WARNING SYSCONFIG.LIB : Defined _DC_CLK_DBL_ to 0 (disabled
> clock doubler recommendation).
> line 27 : ERROR BOARDTYPES.LIB : No ID Block found on the target board.
> line 28 : ERROR BOARDTYPES.LIB : Please contact Rabbit Technical Support
> at http://www.digi.com/support for assistance.
>
> Even sample code like pong.c generated the same error message. Since the
> error seemed board related I switched to my RCM5600W and no errors occured
> at all.
>
> I understand that the ID Block on the RCM6760 has been corrupted but I
> don't know how to fix it. From similiar threads I have learned that I need
> a IDBlock.c or something that clears the ID block.
>
> Is there anyone who have encountered this problem before and have a
> solution or tip for me?
>
> BR,
> Anders
>
>
>
Hi Phil

Thanks a lot. I got a response from Digi as well and they sent me a program too which reinitiated the ID block. Now it works perfectly again :)

BR,
Anders

--- In r..., Phil D wrote:
>
> I corrupted my userID block on a RCM6700 i contacted digi and they gave me
> a program to rewrite the user id block
> ive put it on my dropbox
> http://dl.dropbox.com/u/44413828/WriteIdBlock_1064.zip in the examples it
> says its for RCM67XX so i presume it will work on your 6760. Had to use
> the rabbit field utility with no board verification to upload it to the
> board
>
> Good Luck
>
> Phil
> On 20 January 2012 13:09, flanderso11
> wrote:
>
> > **
> >
> >
> >
> > Hi
> >
> > When debugging my project on my RCM6760 and compiling my modified code I
> > got an unexpected message:
> >
> > line 19 : WARNING SYSCONFIG.LIB : _DC_CLK_DBL_ should always be defined,
> > but was not defined:
> > line 20 : WARNING SYSCONFIG.LIB : Defined _DC_CLK_DBL_ to 0 (disabled
> > clock doubler recommendation).
> > line 27 : ERROR BOARDTYPES.LIB : No ID Block found on the target board.
> > line 28 : ERROR BOARDTYPES.LIB : Please contact Rabbit Technical Support
> > at http://www.digi.com/support for assistance.
> >
> > Even sample code like pong.c generated the same error message. Since the
> > error seemed board related I switched to my RCM5600W and no errors occured
> > at all.
> >
> > I understand that the ID Block on the RCM6760 has been corrupted but I
> > don't know how to fix it. From similiar threads I have learned that I need
> > a IDBlock.c or something that clears the ID block.
> >
> > Is there anyone who have encountered this problem before and have a
> > solution or tip for me?
> >
> > BR,
> > Anders
> >
> >
>


Memfault Beyond the Launch