SAME54 erasing and programming problems

Go To Last Post
3 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

I am working on a custom board with E54 chip.

Unfortunately for the moment i didn't manage to complete any erase action or, even less, programming action.

 

I'working with atmel studio and I'm using ATMEL-ICE as prg/deb via SWD interface.

 

The errors i get are:

 

Trying erasing 

Severity:        ERROR
ComponentId:    20100
StatusCode:    131100
ModuleName:    TCF (TCF command: Device:erase failed.)

Timed out waiting for the chip erase to complete

 

Trying programming (without prior erasing)

Severity:        ERROR
ComponentId:    20000
StatusCode:    0

Verifying Flash...Failed! address=0x0051 expected=0x02 actual=0x82

 

Reading action works fine.

 

My fuse configuration is:

 

AC_BIAS0 = 0x01
ADC0_BIASCOMP = 0x07
ADC0_BIASREFBUF = 0x04
ADC0_BIASR2R = 0x07
ADC1_BIASCOMP = 0x07
ADC1_BIASREFBUF = 0x04
ADC1_BIASR2R = 0x07
USB_TRANSN = 0x09
USB_TRANSP = 0x19
USB_TRIM = 0x06
ROOM_TEMP_VAL_INT = 0x1D
ROOM_TEMP_VAL_DEC = 0x08
HOT_TEMP_VAL_INT = 0x68
HOT_TEMP_VAL_DEC = 0x09
ROOM_INT1V_VAL = 0xFE
HOT_INT1V_VAL = 0xFE
ROOM_ADC_VAL_PTAT = 0xAAF
HOT_ADC_VAL_PTAT = 0xD0C
ROOM_ADC_VAL_CTAT = 0xB3B
HOT_ADC_VAL_CTAT = 0x937
BOD33_DIS = [X]
BOD33USERLEVEL = 0x1C
BOD33_ACTION = RESET
BOD33_HYST = 0x02
NVMCTRL_BOOTPROT = 0
NVMCTRL_SEESBLK = 0x00
NVMCTRL_SEEPSZ = 0x00
RAMECC_ECCDIS = [X]
WDT_ENABLE = [ ]
WDT_ALWAYSON = [ ]
WDT_PER = CYC16384
WDT_WINDOW = CYC16384
WDT_EWOFFSET = CYC16384
WDT_WEN = [ ]
NVMCTRL_REGION_LOCKS = 0xFFFFFFFF

 

SW0_WORD_0 = 0x1E7079D (valid)
SW0_WORD_1 = 0x1B29 (valid)
TEMP_LOG_WORD_0 = 0xFE96881D (valid)
TEMP_LOG_WORD_1 = 0xD0CAAFFE (valid)
TEMP_LOG_WORD_2 = 0xFF937B3B (valid)
USER_WORD_0 = 0xFE9A9239 (valid)
USER_WORD_1 = 0xAEECFF80 (valid)
USER_WORD_2 = 0xFFFFFFFF (valid)

 

Can anyone help me?

 

Cheers and Thanks,

 

Filo
 

This topic has a solution.
Last Edited: Fri. Jun 12, 2020 - 05:52 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bump

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

I finally found a solution.

The problem was simply resolved adding a 0.1uf decoupling capacitor on the VDDIO and VDDANA lines...

 

Now it works perfectly.

 

Cheers,

 

Filo