Error following the reload of EMX firmware files

On of my EMX boards game back from a client and would not boot-up anymore. I quickly found out that the EMX module did not run it’s program.
I Accessed the GHI Bootloader sucessfully, found out that the Tinybooter was corrupted and had to reload it .

When i tried to reload the EMX firmware files within MFDeploy, i get an error after MFDeploy uploaded the CLR,CLR2 and Config.HEX files:

I can see in the last few error lines the following text:

" Flash_Chip initialize: ManufacturerCodeFailure 0x0000002 != 0x0000001f at 0x80000000… "
Can you help me figure out what is happening here?
Thanks,
Jean-Francois

Here if the MFDeploy output when uploading the EMX Firmware files:

Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Chk signature
Signature PASS
Chk signature
Signature PASS
Chk signature
Signature PASS
ERROR:
cpsr=0x000000df
pc =0x0004fa57
lr =0x0004fa5b
r0=0x00000001
r1=0x00000000
r2=0x00000200
r3=0x0004fa57
r4=0xe0010000
r5=0x00000001
r6=0x00000057
r7=0x00000000
r8=0x201fc040
r9=0x00002d14
r10=0x00000080
r11=0x4000003c
r12=0xa0000dc1
sp =0x4000f590
ERROR:
cpsr=0x000000df
pc =0x0004fa57
lr =0x0004fa5b
r0=0x00000001
r1=0x00000000
r2=0x00000200
r3=0x0004fa57
r4=0xe0010000
r5=0x00000001
r6=0x00000057
r7=0x00000000
r8=0x201fc040
r9=0x00002d14
r10=0x00000080
r11=0x4000003c
r12=0xa0000dc1
sp =0x4000f590
[0x4000f590] : 00 00 01 e0 88 4d 00 00 00 a2 4a 04 db f6 02 00 …??M…?J.??..
[0x4000f5a0] : df 00 00 40 00 00 00 00 c8 f5 00 40 01 00 00 00 ?..@ …??.@ …
[0x4000f5b0] : 00 00 00 00 38 0e 00 a0 57 00 00 00 38 0e 00 a0 …8…?W…8…?
[0x4000f5c0] : 57 00 00 00 d8 f5 00 40 00 00 00 00 99 06 01 00 W…??.@ …?..
[0x4000f5d0] : 38 0e 00 a0 6d 5c 05 00 18 0d 19 a0 01 00 00 00 8…?m…?..
[0x4000f5e0] : 6d 5c 05 00 1b 94 01 00 38 0e 00 a0 6d 5c 05 00 m…?..8…?m…
[0x4000f5f0] : 5f 00 00 40 00 00 00 00 28 f6 00 40 01 00 00 00 _…@ …(?.@ …
[0x4000f600] : 00 00 00 00 38 0e 00 a0 57 00 00 00 38 0e 00 a0 …8…?W…8…?
[0x4000f610] : 57 00 00 00 00 ad 00 a0 00 00 00 00 e3 d3 00 00 W…?.?..??..
[0x4000f620] : 38 0e 00 a0 6d 5c 05 00 46 6c 61 73 68 5f 43 68 8…?m…Flash_Ch
[0x4000f630] : 69 70 49 6e 69 74 69 61 6c 69 7a 65 3a 20 4d 61 ipInitialize: Ma
[0x4000f640] : 6e 75 66 61 63 74 75 72 65 72 43 6f 64 65 20 66 nufacturerCode f
[0x4000f650] : 61 69 6c 75 72 65 20 30 78 30 30 30 30 30 30 32 ailure 0x0000002
[0x4000f660] : 30 20 21 3d 20 30 78 30 30 30 30 30 30 31 66 20 0 != 0x0000001f
[0x4000f670] : 61 74 20 30 78 38 30 30 30 30 30 30 30 0d 0a 00 at 0x80000000…
[0x4000f680] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f

Looks like the flash ship maybe damaged somehow! Was this used in extreme heat?

Not that i am aware of… It was installed one month ago, outdoors in a sealed NEMA 4X box and dipped in a protected uretane from Epoxies.com (20-2350 Polyurethane), in Nova Scotia , Canada.

Maximum temperature would have been around 30-35 degrees Celsius.

From what you are telling me, there is some physical damage to the Flash Chip within the EMX module? Any other tests i should do to confirm this?

Jean-Francois

I was only assuming it is damaged. Get into GHI loader and use E to erase all and then reload everything from scratch to be sure.

Hi Gus,

Well, i tried three times erasing the Flash withing the GHI bootloader, before uploading again the CLR,CLR2, Config.HEX . I always an error when MFDeploy says Executing Application after the files upload:

So the final verdict is a blown flash?

MFDeploy debug output:

Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Pinging… TinyBooter
Bootloader build info: GHI Electronics, LLC
Chk signature
Signature PASS
Chk signature
Signature PASS
Chk signature
Signature PASS
ERROR: ABORT Prefetch
cpsr=0x000000df
pc =0x30766964
lr =0x0001942d
r0=0x00000001
r1=0x4000f438
r2=0xa0000e38
r3=0x30766964
r4=0x4f525245
r5=0x5f203a52
r6=0x5f74725f
r7=0x00000000
r8=0x00000000
r9=0x00002d14
r10=0x400000b0
r11=0x00002d0c
r12=0xa0000dc1
sp =0x4000f480
ERROR: ABORT Prefetch
cpsr=0x000000df
pc =0x30766964
lr =0x0001942d
r0=0x00000001
r1=0x4000f438
r2=0xa0000e38
r3=0x30766964
r4=0x4f525245
r5=0x5f203a52
r6=0x5f74725f
r7=0x00000000
r8=0x00000000
r9=0x00002d14
r10=0x400000b0
r11=0x00002d0c
r12=0xa0000dc1
sp =0x4000f480
[0x4000f480] : 0d 0a 00 ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba …?.???.???.???
[0x4000f490] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f4a0] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f4b0] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f4c0] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f4d0] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f4e0] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f4f0] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f500] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f510] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f520] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f530] : 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba 0d f0 ad ba .???.???.???.???
[0x4000f540] : 0d f0 ad ba 0d f0 ad ba c8 f5 00 40 ff ff ff ff .???.???.@ ???
[0x4000f550] : 00 00 00 00 45 57 00 00 ec f5 00 40 c8 f5 00 40 …EW…??.@ ??.@
[0x4000f560] : 08 00 00 00 4c 0d 07 00 00 00 01 e0 01 00 00 00 …L…?..
[0x4000f570] : 57 00 00 00 00 00 01 e0 01 00 00 00 57 fa 04

You uploaded tinybooter as well? Using X command?

Hi Gus,

Yes , i followed all the steps described in the EMX User Manual Rev 1.3 (pages 18 to 25). I tried three time yesterday, i will redo all these time another time this morning.

I was wondering if there was any kind of low-level recovery technique that can be used to further pin-point where the problem lies within the EMX module. If not, well i guess another module will need to be purchased.

Jean-Francois

I an afraid something on the module got damaged.