Main Site Documentation

EMX 4.2.10 RAMC Error


#1

Here’s a debug output from a product that is already with a customer:
RAMC CRC:53c73d78!=616a2f24
RAMC 00:eaffffff
RAMC 04:e59ff010
RAMC 08:baadf00d
RAMC 0c:e59ff00c
RAMC 10:e59ff00c
RAMC 14:baadf00d
RAMC 18:e59ff008
RAMC

This product uses CAN but is not supposed to have ethernet network.

I have already seen this issue do to problem with socket for 4.2.10 sdk but what’s happened here??? no gc fire before…


#2

Did you use in field update maybe?


#3

Yes


#4

My guess is the system was not completely updated properly or updated the system on an old application or updated the application on an old firmware. App and firmware need ot share the same version.


#5

We are doing complete IFU each time. Not only app.hex…

I don’t know how it is possible. What element make you think about ifu trouble? Why not something else?


#6

I am only guessing


#7

Customer send the product back :frowning: .Hope we will succeed to reproduce the issue here…


#8

We succeed to reproduce error after 3hours of execution.


Loop performs in155355 micro seconds
Loop performs in174405 micro seconds
Execution de l'instruction :1000
Affectation de FL1000 à 1: inhibition de l'instruction1000
Affectation de FL1001 à 1: inhibition de l'instruction1001
*****************DATA LOGGING********************
Loop performs in962785 micro seconds
Loop performs in155383 micro seconds
Loop performs in144181 micro seconds
Loop performs in344208 micro seconds
Loop performs in146437 micro seconds
Loop performs in142238 micro seconds
R                ):    408 bytes
********************
nhibition de l'instruction1001
RAMC CRC:53c73d78!=616a2f24
RAMC 00:eaffffff
RAMC 04:e59ff010
RAMC 08:baadf00d
RAMC 0c:e59ff00c
RAMC 10:e59ff00c
RAMC 14:baadf00d
RAMC 18:e59ff008
RAMC

It seems that this time, problem occurs when the Garbage Collector fires:
" R ): 408 bytes"

How to investigate and solve it quickly? (the next and unfortunately the last time slot to reinstall the product is monday next week)

Here’s the config for the EMX:
HalSystemInfo.halVersion: 4.2.0.0
HalSystemInfo.halVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
HalSystemInfo.oemCode: 255
HalSystemInfo.modelCode: 0
HalSystemInfo.skuCode: 65535
HalSystemInfo.moduleSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
HalSystemInfo.systemSerialNumber: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Microsoft Copyright © Microsoft Corporation. All rig
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.10.1
SolutionReleaseInfo.solutionVendorInfo: Copyright © GHI Electronics, LLC
SoftwareVersion.BuildDate: May 1 2013
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: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False

This error seems to stall completely the platform, the board is not reboot by the watchdog. After manual reset:

**************Début de programme à: 09/18/2013 07:45:35
buzTrue
powTrue
the DS binarry formated backup file will be used
#### Exception System.IO.IOException - CLR_E_FILE_NOT_FOUND (1) ####
#### Message:
#### System.IO.FileStream::.ctor [IP: 00f2] ####
#### System.IO.File::ReadAllBytes [IP: 0008] ####
#### USU.Program::Main [IP: 067a] ####
Uncaught exception
Done.
Waiting for debug commands…

It seems problem also occurs during a file writing process.

After switching off/on the power supply, the same thing happens.

I attach a view of the SD CArd after system crashes. The SD is samsung 8GB. The size indicated by windows is therefore totally wrong!!!


#9

After deploying again with visual studio, it runs again till???


#10

Under visual when the problem occurs there’s no message printed. To see it I need to use mfdeploy.

For now under VS the board reboot automatically. without printing anything while on mfdeploy I see the ramc error and the board reboot. It seems that the problem happens during File system write.


#11

Affectation de FL1000 à 1: inhibition de l’instruction1000
Affectation de FL1001 à 1: inhibition de l’instruction1001
DATA LOGGING***
Loop performs in1076135 micro seconds
RAMC CRC:53c73d78!=616a2f24
RAMC 00:eaffffff
RAMC 04:e59ff010
RAMC 08:baadf00d
RAMC 0c:e59ff00c
RAMC 10:e59ff00c
RAMC 14:baadf00d
RAMC 18:e59ff008
RAMC

this shows that problem can also occurs while there’s not filesystem access


#12

I confirm that this is not sd file related… I unplugged the can bus so I do not know where to investigate… I need help from expert that will advice me how to decrypt RAMC message.

I will also check with an other board


#13

This happens to one board but not to other one. May be the EMX module has something broken?


#14

Did you reload the software?


#15

Yes I did. I reinstalled tiny booter and the GHI firmware (config.hex, firmware and firmware 2). and deployed with Visual studio.

After several minutes of execution (sometime just 1-2 min, sometimes more), the RAMC error occurs.

Loop performs in228434 micro seconds
Loop performs in228121 micro seconds
RAMC CRC:53c73d78!=616a2f24
RAMC 00:eaffffff
RAMC 04:e59ff010
RAMC 08:baadf00d
RAMC 0c:e59ff00c
RAMC 10:e59ff00c
RAMC 14:baadf00d
RAMC 18:e59ff008
RAMCUser Cancel...
Connecting to EMX_EMX...Connected
Loop performs in230608 micro seconds


#16

Is it an EMX failure?


#17

Thought about this for a while and I am not sure! The only the we can do now is if you were to send us your device then we can dig deeper into this.


#18

Why not. What about US customs ? Is there any fee to send a custom board to US?


#19

give it a value of $1 in the invoice and explain it is for testing. I think this would work.


#20

Boards have been sent yesterday to you company. Please let me know when you will receive them.

Regards

Jeremie