AnsweredAssumed Answered

Strange behavior Lockbox's unique Chip ID BF512

Question asked by rschoop on Aug 3, 2018
Latest reply on Aug 15, 2018 by rschoop

Hello all,

 

I have a strange situation here where I can not read the  CHIP ID .  Yesterday  I could read this  on this  specific target hardware but  not today .  I use the  ICE-100B  Emulator.   Below the results of the wrong read values .  I was troubleshooting extensively on this target board and  I think maybe a high voltage or current may have damaged the BF512 processor.  I have to say  despite the fact the CHIP ID is not correct the  firmware is working properly with no noticeable issues after booting up. But  when  I  use the same  firmware on a different hardware target then it reads the correct chip id values .  See below for the results for the correct values on a different target using the same firmware.

 

What can be wrong here ?  Maybe the BF512 is damaged ??

Please help.

 

Thanks,

 

rschoop

 

Wrong values  chip id 's :

 

Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            00 00

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            00 00

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            40000000040000004000000004040000 40000000040000004000000004040000

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            40400004040000 40400004040000

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            04040404000000 04040404000000

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            40400004040000040000 40400004040000040000

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            00 00

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            04040404000000 04040404000000

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            404000000404040000 404000000404040000

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            00 00

 

On a different target ,  the correct values :

 

Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            9e2d678b59e20000f0a486238ba0dd02 9e2d678b59e20000f0a486238ba0dd02

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            9e2d678b59e20000f0a486238ba0dd02 9e2d678b59e20000f0a486238ba0dd02

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            9e2d678b59e20000f0a486238ba0dd02 9e2d678b59e20000f0a486238ba0dd02

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            9e2d678b59e20000f0a486238ba0dd02 9e2d678b59e20000f0a486238ba0dd02

           

            Loading: "C:\Users\rschoop\Desktop\Firmware\ FW Testing version A.dxe"...

            Load complete.

            9e2d678b59e20000f0a486238ba0dd02 9e2d678b59e20000f0a486238ba0dd02

Outcomes