E70 Silicon Revision B coming ?

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

I updated ASF from 3.34 to 3.40 when updating AS to 7.0.1931. I was surprised to see that there are a some changes in the E70 header files (after not seen any changes for years...).

Second I noticed that there is a new compiler symbol "__SAME70Q21B__" in the project settings. I compared the project files and found that this was previously "__SAME70Q21__".

 

Now I found in the release note of ASF 3.40 a small "note":

Note: SAME70 Xplained Pro and Examples are moved from Rev A silicon to Rev B. Do Not upgrade to this ASF
release if you are want to use the SAME70 Xplained Pro and Examples with silicon Rev A

Is there any silicon revision B coming which is not compatible with revision A ?

What is the difference between A and B and when is it available ?

How can I make sure that our application still runs on our home brew E70 HW based on silicon rev A after doing an ASF upgrade ?

 

SAME newbie

Last Edited: Tue. Aug 7, 2018 - 08:18 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dear Joe,

 

the version B is already on the market and I guess it will be hard to find the A version nowadays. In the Errata you find all the differences. Main difference affect the MCAN. However, depending on your application, you might be affected with other issues as well.

 

http://ww1.microchip.com/downloa...

 

Best Regards

Markus

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

Hi Markus

 

According to this document version B today is only available for SAMV70 devices. E70/S70 is N/A in table 4.

But in ASF 3.40 there is already a version B include file (ASF\sam\utils\cmsis\same70\include\same70q21b.h) present.

 

What makes me wonder is the warning in the ASF release notes, see my first post concerning the SAME70-XPLD.

And in my opinion it should always be possible to update to the latest ASF although version A is used as HW platform.

 

I guess all I have to do is to switch "__SAME70Q21B__" back to compiler symbol "__SAME70Q21__". This makes sure that the correct include file is compiled, see file same70.h.

 

A quick diff between \ASF\sam\utils\cmsis\same70\include\same70q21.h

 

#define __SAM_M7_REVB           0      /**< SAME70Q21 Revision A */
#define CHIP_CIDR   (0xA1020E00UL)

and ASF\sam\utils\cmsis\same70\include\same70q21b.h

#define __SAM_M7_REVB           1      /**< SAME70Q21 Revision B */
#define CHIP_CIDR   (0xA1020E01UL)

Version B has additional interrupts defined

  I2SC0_IRQn           = 69, /**< 69 SAME70Q21B Inter-IC Sound Controller (I2SC0) */
  I2SC1_IRQn           = 70, /**< 70 SAME70Q21B Inter-IC Sound Controller (I2SC1) */
  GMAC_Q3_IRQn         = 71, /**< 71 SAME70Q21B Gigabit Ethernet MAC (GMAC) */
  GMAC_Q4_IRQn         = 72, /**< 72 SAME70Q21B Gigabit Ethernet MAC (GMAC) */
  GMAC_Q5_IRQn         = 73, /**< 73 SAME70Q21B Gigabit Ethernet MAC (GMAC) */

The question remains why AS7 update switches the project automatically to version B although this version is not available yet.

My assumption is that applications compiled for version B using "__SAME70Q21B__" compiler symbol still run on silicion version A if no version B features or improvements (e.g. MCAN) are used.

 

A quick test shows me that our application compiles and runs no matter "__SAME70Q21__" or "__SAME70Q21B__" is defined. I'll test more applications soon and go deeper into the erratas.

Our silicon dealer claimed in the past that there are no erratas in version A which might affect us and therefore there will be no version B in the near future.

I'm surprised to see some erratas regarding the AFEC and TWI peripherals which are heavily used by our applications.

 

At the moment our silicon dealer says that still E70 version A silicon is sold. I'll add some verification code to distinguish between version A and B in order to get informed if and when version B silicon is available on our boards.

 

Thanks

SAME newbie