Main Site Documentation

RAMC CRC & ERROR: Undef Instr


#1

[ul]On one of my Fez Spider Boards I am receiving weird errors:
RAMC CRC:da2b95ff!=ce6a5202
RAMC 00:00010010
RAMC 04:baadf00d
RAMC 08:4000f748
RAMC 0c:00000000
RAMC 10:e59ff00c
RAMC 14:e59ff00c
RAMC 18:00000000
RAMC 1c:baadf00d
ERROR: Undef Instr
cpsr=0x00000010
pc =0x00000000
lr =0x00000004
r0=0x00000004
r1=0xc7a5d1da
r2=0xa00000df
r3=0x00000000
r4=0x00000000
r5=0x00000000
r6=0xe59ff00c
r7=0xe59ff00c
r8=0x00000000
r9=0xbaadf00d
r10=0xe59ff008
r11=0x0000a8ad
r12=0x00000004
sp =0x4000ffd8
ERROR: Undef Instr
cpsr=0x00000010
pc =0x00000000
lr =0x00000004
r0=0x00000004
r1=0xc7a5d1da
r2=0xa00000df
r3=0x00000000
r4=0x00000000
r5=0x00000000
r6=0xe59ff00c
r7=0xe59ff00c
r8=0x00000000
r9=0xbaadf00d
r10=0xe59ff008
r11=0x0000a8ad
r12=0x00000004
sp =0x4000ffd8
[/ul]
[ul]I am connected via .Net Micro Framework Deployment Tool on serial port. I can easily reproduce the issue within a few minutes. Device capabilitites:
HalSystemInfo.oemCode: 255
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 65535
HalSystemInfo.moduleSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
HalSystemInfo.systemSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ClrInfo.clrVersion: 4.3.1.0
ClrInfo.clrVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.3.1.0
SolutionReleaseInfo.solutionVersion: 4.3.3.0
SolutionReleaseInfo.solutionVendorInfo: Copyright © GHI Electronics, LLC
SoftwareVersion.BuildDate: Jul 29 2014
SoftwareVersion.CompilerVersion: 410713
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 0
LCD.Height: 0
LCD.BitsPerPixel: 0
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: True
ProfilingAllocations: True
ProfilingCalls: True
IsUnknown: False
[/ul]

[ul]
When the issue occur I am loosing connection via .Net Microframework Deployment Tool. Ping, Rebbot CLR commands does not work. I must press reset button on Fez board
[/ul]


#2

Can you reapply firmware and not deploy an application to it, and does the issue still occur ? If so, then it is possibly hardware… anything else special about this one of your spiders and not the other/s?