ATXMEGA128A3U-MH out of stock, no more until October?!

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

The ATXMEGA128A3U-MH seems to be out of stock everywhere! What is going on?

 

Since Microchip took over, prices have rocketed and now they can't even make enough of the damn things to satisfy demand. What are we supposed to do until November?!

 

Does anyone know what is going on at Microchip/Atmel these days?

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

"Dare to be naïve." - Buckminster Fuller

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

mojo-chan wrote:
What are we supposed to do until November?!
Re-package, if possible, then port.

 

Some distributors of EOL and NRND parts may estimate that a part will expire then begin buying stock.

Rochester Electronics has significant XMEGA stock :

https://buy.rocelec.com/parts/ATM/ATXMEGA128A3U-AUR/ATMATMATXMEGA128A3U-AUR

Likewise at Ewing Components :

http://www.ewinginc.com/searchn.php?part=ATXMEGA128A3U&x=0&y=0

 

Are there PIC24 that could replace ATXMEGA128A3U-M?

 

P.S.

mojo-chan wrote:
... November?!
or October for new stock from Microchip (minimums of one tray) :

https://www.microchipdirect.com/ProductDetails.aspx?Category=ATXMEGA128A3U&Sort=PackageType&PackageType=VQFN

 

"Dare to be naïve." - Buckminster Fuller

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

I have a massive, well tested, mature application that I don't want to change now... But we can't not make any until November, so I'm going to have to port to the 256A3U.

 

Gaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaagh

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

Indeed, Octopart shows your scarcity.

 

For less than a buck more, you can get the '256:

And there are some '64 in stock at about half the price of the '256.

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

I'm going to have to port to the 256k device, and then manage having two types of device with two different firmwares in the field...

 

To be fair I was thinking about doing a special 64k cost reduced version anyway, but it's annoying to be forced just for the sake of Microchip screwing up production for a few months. The fact that they have been cranking the prices up is just the icing on the turd.

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

mojo-chan wrote:

I'm going to have to port to the 256k device, and then manage having two types of device with two different firmwares in the field...

Won't they both use the same firmware?

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

I'm looking at using the same firmware on both... There will need to be some checks because there is a bootloader, which has to be loaded at a different location on each. The main app calls functions in the bootloader for a few tasks.

 

The 256k version uses a little more current at idle, but it still fits my budget. Not sure if there are any other traps.

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

Does the application use functions in the bootloader because there was no room in the application memory, or because you want to write to things only a bootloader can do?

 

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

The latter. It needs to save some data into the User Signature Row and also to update the bootloader itself.

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

Maybe there is a way for the application to find out which chip it is running on so it can know how high to jump to get to the bootloader.  The device ID in the MCU control registers could be used to find out which chip it is on.

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

That's what I've done. Check the MCU ID and set registers appropriately. I don't think any of the assumptions made by the compiler will cause problems.

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

mojo-chan wrote:
.....is just the icing on the turd.

 

LMAO!!  I just shot tea all over the place from laughing!

 

I too have been burned by Micromel/Atchip just recently as well.

 

Thanks for the laugh though.  I needed that.

 

JIm

If you want a career with a known path - become an undertaker. Dead people don't sue! - Kartman

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user

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

or October for new stock from Microchip (minimums of one tray) :

Now mid-Sep-2017 :

http://www.microchipdirect.com/ProductSearch.aspx?keywords=ATXMEGA128A3U-MH

"Dare to be naïve." - Buckminster Fuller

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

I'm more inclined to believe rand() than Atmel/Microchip availability dates these days.