Skip to main content
David Staffenberger
Associate II
August 16, 2017
Solved

Can't activate FLASH/OTP Device !

  • August 16, 2017
  • 3 replies
  • 4803 views
Posted on August 16, 2017 at 11:06

Hello community,

I have 2 SPC56EL70L5-DISP boards and I am messing around with FlexRay.

Today I was not able to program one of the boards anymore (with the same code as the other board).

0690X00000607oDQAQ.png

The UDE Memtool shows the error stated in the picture above.

Furthermore the UDK STK 4.8 gives the following results:

We 16.08.2017 10:42:13.339, Error, Core::PFLASH, Error message from FLASH driver, command 'Init': We 16.08.2017 10:42:13.339, Error, Core::PFLASH, FLASH/OTP operation failed We 16.08.2017 10:42:13.339, Error, Core::PFLASH, Initializing FLASH driver on target failed We 16.08.2017 10:42:13.339, Warning, Core::UDEMemtool, FLASH programming for device '2 MByte OnChip PFLASH (Starterkit)' not available ! We 16.08.2017 10:42:13.339, Success, Core::UDEDebugServer, Connection to SPC56EL70 target established: PowerPC Target, JTAG-ID: 0x0AEA9041 We 16.08.2017 10:42:14.288, Warning, Core::PpcJtagTargIntf, Write access to memory range 0x00000000-0x001FFFFF refused ! We 16.08.2017 10:42:14.304, Warning, Core::UDEDebugServer, CRC check after download failed in memory range from 0H to 3F75H! We 16.08.2017 10:42:14.304, Warning, Core::PpcJtagTargIntf, Write access to memory range 0x00000000-0x001FFFFF refused ! We 16.08.2017 10:42:14.320, Warning, Core::UDEDebugServer, CRC check after download failed in memory range from 3F80H to 418BH! We 16.08.2017 10:42:14.320, Warning, Core::PpcJtagTargIntf, Write access to memory range 0x00000000-0x001FFFFF refused ! We 16.08.2017 10:42:14.320, Warning, Core::UDEDebugServer, CRC check after download failed in memory range from 4190H to 428BH! We 16.08.2017 10:42:14.335, Success, Core::UDEDebugServer, Program with ID 0x1 - code size 17022 bytes - was loaded!

Has anyone ideas what my problem might be? Is the flash dead?

Because the controller seems to be powered properly, I checked every jumper to be on the same position as on the other board and the UDK STK seems to recognise the controller correctly.

Thank you in advance,

best regards,

David.

##spc56 #flash #programming
This topic has been closed for replies.
Best answer by david tomsa
Posted on August 21, 2017 at 08:02

I have found the problem. The Problem wasn't the UDE, IDE, ... . It was the Source code. I changed the Init code (crt0.S File). My change blocked the access to the flash. 

3 replies

david tomsa
Associate III
August 18, 2017
Posted on August 18, 2017 at 07:18

I have the same Problem. I'm not able to debug from Eclipse. I get the Error like the post above and this issues 

Message from component 'PpcJtagTargIntf' :

Can't connect target !

Message from component 'PpcJtagTargIntf' :

Failed to open communication channel !

Message from component 'FtdiCommDev' :

Requested protocol is not supported

When i use the UDE Visual Plattform, i'm able to erase and flash the Controller. But i have to create everytime a new Workspace for that. Then, i'm able to erase/flash for one time. 

David Staffenberger
Associate II
August 18, 2017
Posted on August 18, 2017 at 07:36

Hello,

thank you for your suggestion but unfortunately that does not change my errors.

I think that my board broke and I already ordered a new one. But I am still interested in wheter the board is broke or if I did something wrong.

Best Regards,

David.

david tomsa
Associate III
August 18, 2017
Posted on August 18, 2017 at 09:18

We have the Problem with the SPC70 Eval Board an our Hardware. I can't imagine that our Hardware and our Board is broken, beacuse sometimes it works. 

david tomsa
david tomsaBest answer
Associate III
August 21, 2017
Posted on August 21, 2017 at 08:02

I have found the problem. The Problem wasn't the UDE, IDE, ... . It was the Source code. I changed the Init code (crt0.S File). My change blocked the access to the flash. 

David Staffenberger
Associate II
August 21, 2017
Posted on August 21, 2017 at 08:11

Good to hear, I will mark this thread as answered since I assume that my board broke.