ATmega324P-B15AZ support?

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

How can I get Atmel Studio 7.0 to support device ATmega324P-B15AZ?  Note that this is pbautomotive, P-B, not PB.  Links to P-B and PB:

 http://www.atmel.com/devices/atmega324pbautomotive.aspx

 http://www.atmel.com/devices/atmega324pb.aspx

 

It finds a device signature for what it thinks is a PA, 0x1E9511.

I've checked for updates to Studio, and updated all the device packs, but it still tries to treat the ATmega324P-B15AZ as a PA.

 

Please advise,

 

 

John

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

Are you sure it is not just a Mega324P with updated specifications for the automotive business?

the A only means that it has had a update and probably is produced in a different factory with regard to the original P version.

 

You could ask your distributor or atmel contact what is the difference, but you could also have a look in the datasheets and check in the register overview and instruction set overview that all the registers and instructions present on the PA devices are also there on your automotive chip.

My guess is that this will be the same as the chip identifier should be unique for each chip with unique features.

 

I have had Mega644 automotive class once as a sample. the distributor could not get me samples of the 'normal' version but gave me samples for automotive use. He then tolled me that I could use the normal P version as chip base and that there only were small differences in the overall specification, but that registers/programming space and memory were ok.

 

 

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

Well, I initially did select ATmega324P as the device, but it gives me:

 

 

Here's a photo of the chip: 

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

According to both datasheets the ATmega324PA and the ATmega324P-B (automotive) have the same signature so you could select the PA version I guess.

 

ATmega324P-B 0x1E 0x95 0x11
ATmega324PA 0x1E 0x95 0x11
 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Thanks, that gets me further, but the Fuses page shows differing values than we see with our P devices. The Fuse Register Extended is the same value, but for HIGH and LOW it shows 0x99 and 0x62, which differs from our P device settings.  I'm not knowledgeable enough about those to know how to proceed.

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

Thanks, that gets me further, but the Fuses page shows differing values than we see with our P devices. The Fuse Register Extended is the same value, but for HIGH and LOW it shows 0x99 and 0x62, which differs from our P device settings.  I'm not knowledgeable enough about those to know how to proceed.

Huh?  The datasheets for the all the variants (P/PA/P-B) show that the fuses are identical.  Even the default values for the fuses are the same, except for the extended fuse, which contains only the BOD fuse bits.  The automotive device has BOD@2.5V enabled by default.

"Experience is what enables you to recognise a mistake the second time you make it."

"Good judgement comes from experience.  Experience comes from bad judgement."

"Wisdom is always wont to arrive late, and to be a little approximate on first possession."

"When you hear hoofbeats, think horses, not unicorns."

"Fast.  Cheap.  Good.  Pick two."

"We see a lot of arses on handlebars around here." - [J Ekdahl]

 

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

I see there's a new update to Atmel Studio. I installed that (version 7.0.784) and with it came a new ATmega device pack (version 1.0.98).  But still no joy.