Problems changing from ATSAMD20E15A to ATSAMD20E15B

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

Hi.

I have developed a pcb with an ATSAMD20E15A for a hand tool and sold about 1800 of this card without any problem but with the lack of processors we had to buy 500 pcs of ATSAMD20E15B which, as I understood, should be fully compatible.
We have now mounted 500 cards with this processor and on microchip studio I changed device to this processor, compiled and linked the firmware but when trying to start to debug I got the message;
"Failed to launch program.
Error: Unexpected Chip Identifier 0x10001600 (expected 0x1000160D)."

To eliminate any firmware problem I started a new solution/project with this processor selected and with just the standard empty while{} I still get the same error.

I will be very happy for all suggestions how to solve this problem for as I said; There are 500 pcbs mounted and customers waiting.

Best regards. Gunde

GundeNilsson

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

Hi Gunde, I have experienced something similar, going from ATSAMD21G18A to ATSAMD21G16B - the chip identifier works ok for me, though. My problem is that the verify shows a different result from the programming, and it's a few bytes on specific locations. 

What programmer hardware are you using?

What software?

In my case, I use Microchip Studio, and when I try using a wrong chip type, it displays a Dialog box with the correct type I should use. Perhaps you are not compiling or setting it properly somewhere. 

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

Hi Rick and thank you for your answer.

At first I used Atmel studio, have done work/projects with this even before Atmel was bougth by Microchip,  and Atmel-ICE and changed the chip in the dialogue from ATSAMD20E15A to ATSAMD20E15B.
Cleaned both solution and project, builded the project first in debug mode which didn't work when I tried to download and run it and after that in relaese mode with the same result.

Cleaned the harddrive from Atmel Studio and made a fresh dowload with Microchip studio, downloaded updated packs and tried the above once more.
Tried to program the chip through TOOLS/ device programing with the same result.

Normaly when we change from one processor to another we make some test boards but we thougth this would be a minor change and now we have 600 boards waiting with this processor soldered and customers waiting.
The reason for the change was that we couldn't find the earlier used processor on the market then.

Have startet a case with microchip support and hope they will come up with a solution.

Best regards. Gunde

GundeNilsson

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

Hi Gunde, can you post a visual snapshot or a logfile to understand better? I think that "doesn't work" is a very generic statement. From what I understand, your project compiles ok. Then, when you open the "Device Programming" Dialog, you click to read the Device signature and it doesnt match with the expected signature. Does this fit with your problem?

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


Hi Rick.


Yes, that is a correct understanding.


Compiling, linking works without errors but when I try to start debug or download the code through Tools/programming I get this message



The only function without this error is to erase the memory on the chip through tools


Br. Gunde

 

GundeNilsson