Problem on Xmega behavior after Lock Bits program

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

Hi folks, I am using an ATxmega128A4U which is programmed using an Atmel ICE.

 

To make sure everything was going on correctly with the Lock Bits Programming I am doing this phase manually at the Lock Bits section.

Currently, I am programming with the value 0x56:

Boot Section - Read not allowed

Application Section - Read not allowed

Application Table - Read not allowed

Lock Bits Section - Write not allowed

 

Therefore I can check the Lock Bits after programming and they do burn correctly.

 

The problem arises when I try to update the application (update the firmware) without erasing the chip: it does not update anything...

 

Does anyone have any idea about what is happening?

 

Thank you for your time, Felipe.

Regards!
FS.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

F Schneider wrote:
I try to update the application (update the firmware) without erasing the chip

How can you update without erasing?  Flash memory can only change from a 1 to a 0, to get back to a 1, you must erase the flash page!

 

Jim

 

Click Link: Get Free Stock: Retire early! PM for strategy

share.robinhood.com/jamesc3274
get $5 free gold/silver https://www.onegold.com/join/713...

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Alright, for that you can mark the option Erase Flash before programming.

 

My point is: without the lockers, you can just hit Program and everything works fine. When you lock only the read process, the write also become nonfunctional. 

Regards!
FS.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

F Schneider wrote:
without the lockers, you can just hit Program and everything works fine. When you lock only the read process, the write also become nonfunctional. 

Yes that is right, in order to write, you have to be able to read to see what bits are 1's, so if it is read locked, it is also write locked. and your not able to verify the writes....

If it is write locked, you can read, but not wirte...

 

Jim

 

 

Click Link: Get Free Stock: Retire early! PM for strategy

share.robinhood.com/jamesc3274
get $5 free gold/silver https://www.onegold.com/join/713...

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes that is right, in order to write, you have to be able to read to see what bits are 1's, so if it is read locked, it is also write locked. and your not able to verify the writes....

If it is write locked, you can read, but not wirte...

 

Ji

 

It does not make sense, for what reason has Xmega lock bits to avoid the reading process then?

Regards!
FS.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It revealed a much worse case than I though:

 

Xmega read lock bits does not avoid the reading process... We have sent to the marked about 20 product samples without lock bits protection... The only wait to avoid the reading is to block the Read and Write process, what makes a lot harder to update the software!!!

Regards!
FS.