Standalone atprogram (again)

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

I have been using a standalone atprogram for a while. It's from a 6.2 Studio and the USB drivers:
  from http://ww1.microchip.com/downloa...
  from https://www.microchip.com/mplab/...

It looks that I need to upgrade it because I need it to work with the new chips and UPDI.
- Will the newer atprogram work with the old (driver-atmel-bundle-7.0.888.exe) driver?
- Is there is way to install a new driver bundle without installing the Studio?

 

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

Atmel-ICE and AVRISP mkII.
Atmel-ICE currently only for SAMDs. And now I plan to use them for the 0-series too.
AVRISP mkII for other AVRs (I have a bunch of them, I really like them much better than Atmel-ICE, and I want to keep using them)

 

Edit: That is weird. I thought I saw a reply and was replying to the reply. Now I don't see what I replied to.

Last Edited: Wed. Apr 17, 2019 - 01:04 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I removed my post as i felt it was not relevant to your question.

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

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

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

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

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

OK, installed the latest Studio (7.0.1931).
Copied stuff per https://microchip.secure.force.c...
Trying to run atprogram. It says:
[ERROR] Could not find atbackend.exe

The above web page says "Go to Command prompt browse the atbackend folder". Do I really have to? The old version worked without that.

 

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

Set a PATH

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

"Set a PATH" - I'll if I don't find a better way. It's just annoying that the whole atprogram setup is so over-complicated. And earlier versions worked just fine without messing with the PATH.

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

OK, besides the path, everything else seems to work.
The drivers are at: https://gallery.microchip.com/pa...
There is a zip file there that includes the following:
      driver-atmel-installer-x64-7.0.1645.msi
      driver-libusb0-installer-x64-7.0.1645.msi
      driver-mplabcomm-installer-7.0.1645.exe
      driver-segger-installer-x64-7.0.1645.msi
      driver-winusb-installer-7.0.1645.msi
At first I installed all of them except mplabcomm. AVRISP mkII showed up in Device Manager under Atmel. But atprogram didn't see it. I almost gave up and was about to post more questions here. Then decided to install the mplabcomm too. That was it!

 

Anybody knows what that mplabcomm thing is? I also see that unlike the other 4 it doesn't even show in the list of installed products under Programs and Features?

 

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

It's the USB stack from MPLAB... The name is pretty revealing..
.
It handles the WinUSB (former Jungo) devices.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

Last Edited: Thu. Apr 25, 2019 - 02:45 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If mplabcomm handles the WinUSB, what does driver-winusb-installer-7.0.1645.msi (Atmel WinUSB) do?

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

It binds the devices to WinUSB (inf + DifX).

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

Apparently there is also a command line option:  -ab --atbackend <arg>      Specify path to atbackend executable.