Atmel Studio 6.2 SP2 Released

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

The customary bells and whistles sumup of Atmel Studio 6.2 SP2 (Release notes) :)

 

New things

  • New ASF.
  • Added full support for the SAML21 family (ultra super-duper low power).
  • Added support for the SAMV7 family (based on the new Cortex-M7 architecture).

 

Bugfixes

  • AVRSV-5685 Fix flash page corruption when connection with SAM-ICE (and other Segger debuggers).
  • AVRSV-5893 Interrupts continue to be disabled after stepping.
  • AVRSV-5923 Programming throws up an error saying that the device id is wrong. Programming completes successfully.
  • AVRSV-6015 Greatly improved compile time (especially when parallel make is enabled).
  • AVRSV-6020 Some fixes for programming files whose path contains non-ascii (debugging is still not working correctly for these files).

 

Downloads

  • Smallest, MD5: 744be50ba06c4d5e6d2cfdcb1679a0fb, SHA1: 50845a322e1d3f3f5223c623a1214fa5a54f0bc5
  • Biggest, MD5: b99be482a801f0f394af12cc67ddd532, SHA1: c567fb6c14124cc5f5a4efb6dddb6c135074526b

 

:: 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

meolsen wrote:

  • AVRSV-5685 Fix flash page corruption when connection with SAM-ICE (and other Segger debuggers).

 

I've been having trouble with Segger J-Links not reading back SAM R21 flash properly - could this be the same problem?

 

My problem is noticed when using the Atmel Studio 6.2 SP1 'Device Programming' dialogue: the verification fails, and using the 'Read' facility gives a hex file showing that the first K or two is wrong.

 

But the programming done automatically by the debugger reports no problems - and the code does, in fact, work properly.

 

Hence it appears the the programming does work, and it's just the read-back that is faulty?

 

It also appears that the debugger is using a different verification method - not a straight read-back - which is why it doesn't see the problem?

 

 

meolsen wrote:
SAM-ICE (and other Segger debuggers).

Can you confirm that a SAM-ICE is, in fact, a "badged" J-link?

 

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Full description of the bug is:

Quote:
Issue #AVRSV-5685: The first flash page can be corrupted by re-connecting with a SAM-ICE after a programming session. Problem is seen in relation to reading the CoreSight ROM table, which is done during the connect sequence.

But our issue can be seen just using the  'Device Programming' dialogue.

 

Still under  'Known Issues':

 

Quote:
Issue #AVRSV-4037: Using a SEGGER tool, after a chiperase in the programming dialogue, reading device flash to file does not reflect the true (erased) state of the device.

 

Which also sounds similar - except that we see the problem with *any* read - not just reading an erased device.

If this is still a 'Known Issue', it suggest that the underlying problem is not really fixed yet?

 

And this:

 

Quote:
Issue #AVRSV-5050: Starting the process by selecting "Start Debugging and Break" or "Start Without Debugging" does not perform flash memory verification.

 

This suggests that the debugger does not verify at all - which would explain why we can program using the debugger.

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the heads up just downloaded it and compiled my EEPROM Programmer solution, that I put on Projects page recently (shameless plug) and you where right about the improved build times.

Runs like a scalded dog now...

Happy Trails,

Mike

JaxCoder.com

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

The underlying problem in AVRSV-5685 came from us initating a read of the CoreSight ROM table on the next connect (discovery of the on-chip debug system), which due to some strange access (reading 8 bit vs 32 bit) caused the first flash page to corrupt.

 

What you are seeing is the cache mechanism used by the JLink (Segger) to read/verify, and a issue where we let the core run a bit between program and verify (shortly told, I haven't been involved in the AVRSV-4037 issue).

:: 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

Can you confirm that a SAM-ICE is, in fact, a "badged" J-link?

It says 'Developed by SEGGER' on it, and it adheres to the JLink API. I don't know much more (or really care...)

:: 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

Runs like a scalded dog now...

Brilliant :)

:: 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

Scalded cats run faster than scalded dogs.   (at least in the U.K.)

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

Hi Morten,

 

Sorry to bother you with such a trivial question, but does the SP2 upgrades the previous version (be it 6.2, or 6.2SP1) ? Or does it install side by side ?

 

Thank you

Have a nice day,
Kraal

Last Edited: Wed. Feb 4, 2015 - 02:34 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Updates (we do not even try to get service packs to go alongside eachother). 6.1.x installs alongside 6.2.x, but for differences on 'build', we upgrade. (basically following normal MSI rules)

:: 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

meolsen wrote:

Can you confirm that a SAM-ICE is, in fact, a "badged" J-link?

It says 'Developed by SEGGER' on it, and it adheres to the JLink API. I don't know much more (or really care...)

 

Segger says,

 

Segger wrote:

J-Link OEM versions

There are several different OEM versions of J-Link on the market. The OEM versions look different, but use basically identical hardware. 
Some of these OEM versions are limited in speed, some of these can only be used with certain chips and some have certain add-on features enabled, which normally requires license. 
In any case, it should be possible to use the J-Link software with these OEM versions. However, proper function cannot be guaranteed for OEM versions.

SEGGER Microcontroller does not support OEM versions; support is provided by the respective OEM.

 

https://www.segger.com/jlink-oem...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you Morten.

Have a nice day,
Kraal

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

Segger says,

Don't you see that I'm meandering around the question itself :)

:: 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

just in case anyone else was interested...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:

The customary bells and whistles sumup of Atmel Studio 6.2 SP2 (Release notes) :)

 

New things...

 

Are the version 7.0 USB drivers included as part of these new things, or do we have to run the installer for them separately?

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

Are the version 7.0 USB drivers included as part of these new things, or do we have to run the installer for them separately?

Included.

:: 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

ASF did not install correctly with the upgrade as I lost the New Example Project... option from the Start Page and was unable to run the ASF wizard in any projects.

 

Downloading/Running ASF from the extension manager prompted me to repair or uninstall.  I selected repair, restarted AS, and still ASF was not installed, had to uninstall/reinstall ASF to get it working again.

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

Last Edited: Wed. Feb 4, 2015 - 06:45 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

larryvc wrote:

ASF did not install correctly with the upgrade as I lost the New Example Project... option from the Start Page and was unable to run the ASF wizard in any projects.

 

Downloading/Running ASF from the extension manager prompted me to repair or uninstall.  I selected repair, restarted AS, and still ASF was not installed.  I had to uninstall/reinstall ASF to get it working again.

Hmmm, strange. do you want me to pass it on, or do you want to open a support ticket (I can't promise to follow up, but support can).

:: 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

Hmmm, strange. do you want me to pass it on, or do you want to open a support ticket (I can't promise to follow up, but support can).

Perfect place for this reply.

 

Not my job!cheeky  Pass it on if you would.

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

After staring Studio6.2Sp2, the first time that any tab in the 'Project->...Properties' window (Build/Build Events/Toolchain/Device/Tool/Advanced) is selected, it uses 50% CPU for about 15 seconds before anything becomes visible. (Win-XP system)


For AVR32 projects, the generated Makefile is always creating a .map file (The state of the 'Generate Map file (-Map)' option in 'Project->...Properties->Toolchain->AVR32/GNU Linker' is being ignored)

Last Edited: Thu. Feb 5, 2015 - 02:38 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 2

Sigh, have to revive this. 

 

The incoming error reports on SP2 has been too high, so it has been decided to release a SP2.1. This is in final testing at the moment at should be available in the next couple of days (tm).

 

Issues include:

  • USB Driver installer. I have posted the updated (7.0.666) here other places and on the gallery. Causes no tool to be shown (even simulator) since atbackend crashes.
  • ASF de-registering from Atmel Studio. Happens if the ASF from SP1 has been updated with the one on the gallery.
  • Atmel Kits not showing or not being up to date.
  • atprogram failing on hex files with segments (basically, we have had issues with segmented hex files that were fixed for SP2, but atprogram had an additional check that we missed removing).

 

Note that we will uninstall previous service packs in this release, since parts of the issues seen in SP2 comes from things lingering from SP1.

 

I'll update here once everything is in place.

 

Lastly, sorry for notifying so late. Have been quite a busy week and a half making sense of it all. 

:: Morten

 

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

Last Edited: Tue. Feb 17, 2015 - 07:00 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I had the same problem after upgrading to Atmel Studio 6.2 SP2. The "New Example Project" disappeared. I just (re)downloaded the latest version of ASF and selected repair. After the repair completed, I opened Atmel Studio and the "New Example Project" was there again.

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

meolsen wrote:
release a SP2.1 ... is in final testing at the moment at should be available in the next couple of days (tm) ...

 

I'll update here once everything is in place.

Anything to report yet?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Oh yes, it ended up on atmel.com late last friday (European time)

:: 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

Meolsen,

 

is this SP2 build 1563 ?

this is the only version I see when going to the studio 6 page at atmel.com

It is talking about SP2 though and not sp2.1

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

Politics :( 1563 is the correct (latest) SP2

:: 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

Thanks for sorting out the politics ;)

 

 

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

We've suffered a major setback with 6.2 SP2 - our device 'SAM3S2A' no longer compiles with the error '#error Unsupported device' (from interrupt.h). It seems the board define path has changed. The same problem occurs with a blank starter ASF gcc project. The project compiles fine in SP1. Attempting to manually define (SAM, SAM3, etc.) creates re-define errors. The only solution we have found is to roll back to SP1.  

 

Am I missing something or is this a bug?

 

Thanks.

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

tuna fish,

 

are you talking about Sp2 or Sp2.1?

As meolsen already pointed out there is a lot of troubles with the first SP2 update.

Did you check the latest version?

 

 

 

 

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

Ok,  did a quick test.......

I might be doing somethign wrong still, but.

I started a new project. selected a general C GCC project and then selected the SAM3S2A as my processor.

The project is created, but I get 15 warnings about stuff being re-defined.......

 

I  below posted a piece of code from the file "sam3s2a.h"

To my opinion this should be a file that one does not need to change.........

 

/* ************************************************************************** */
/*   ELECTRICAL DEFINITIONS FOR SAM3S2A */
/* ************************************************************************** */

/* Device characteristics */
#define CHIP_FREQ_SLCK_RC_MIN           (20000UL)
#define CHIP_FREQ_SLCK_RC               (32000UL)
#define CHIP_FREQ_SLCK_RC_MAX           (44000UL)
#define CHIP_FREQ_MAINCK_RC_4MHZ        (4000000UL)
#define CHIP_FREQ_MAINCK_RC_8MHZ        (8000000UL)
#define CHIP_FREQ_MAINCK_RC_12MHZ       (12000000UL)
#define CHIP_FREQ_CPU_MAX               (64000000UL)
#define CHIP_FREQ_XTAL_32K              (32768UL)
#define CHIP_FREQ_XTAL_12M              (12000000UL)

/* Embedded Flash Write Wait State */
#define CHIP_FLASH_WRITE_WAIT_STATE     (6U)

/* Embedded Flash Read Wait State (VDDCORE set at 1.65V) */
#define CHIP_FREQ_FWS_0                 (17000000UL) /**< \brief Maximum operating frequency when FWS is 0 */
#define CHIP_FREQ_FWS_1                 (30000000UL) /**< \brief Maximum operating frequency when FWS is 1 */
#define CHIP_FREQ_FWS_2                 (54000000UL) /**< \brief Maximum operating frequency when FWS is 2 */
#define CHIP_FREQ_FWS_3                 (64000000UL) /**< \brief Maximum operating frequency when FWS is 3 */

/* HYSTeresis levels: please refer to Electrical Characteristics */
#define ACC_ACR_HYST_50MV_MAX	          (0x01UL)
#define ACC_ACR_HYST_90MV_MAX           (0x11UL)

/* Device characteristics */
#define CHIP_FREQ_SLCK_RC_MIN           (20000UL)
#define CHIP_FREQ_SLCK_RC               (32000UL)
#define CHIP_FREQ_SLCK_RC_MAX           (44000UL)
#define CHIP_FREQ_MAINCK_RC_4MHZ        (4000000UL)
#define CHIP_FREQ_MAINCK_RC_8MHZ        (8000000UL)
#define CHIP_FREQ_MAINCK_RC_12MHZ       (12000000UL)
#define CHIP_FREQ_CPU_MAX               (120000000UL)
#define CHIP_FREQ_XTAL_32K              (32768UL)
#define CHIP_FREQ_XTAL_12M              (12000000UL)

/* Embedded Flash Read Wait State (VDDCORE set at 1.20V) */
#define CHIP_FREQ_FWS_0                 (20000000UL)  /**< \brief Maximum operating frequency when FWS is 0 */
#define CHIP_FREQ_FWS_1                 (40000000UL)  /**< \brief Maximum operating frequency when FWS is 1 */
#define CHIP_FREQ_FWS_2                 (60000000UL)  /**< \brief Maximum operating frequency when FWS is 2 */
#define CHIP_FREQ_FWS_3                 (80000000UL)  /**< \brief Maximum operating frequency when FWS is 3 */
#define CHIP_FREQ_FWS_4                 (100000000UL) /**< \brief Maximum operating frequency when FWS is 4 */
#define CHIP_FREQ_FWS_5                 (123000000UL) /**< \brief Maximum operating frequency when FWS is 5 */

A large number of difenes are indeed double........

more hair raising is that a number of defines have different data.

 

I am also puzzled......

 

My first guess is that someone decided to clean up the mess that these files were in the past and has accidentally removed things that should not have been removed.... Or a copy past error has been made......

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

meslomp wrote:

tuna fish,

 

are you talking about Sp2 or Sp2.1?

As meolsen already pointed out there is a lot of troubles with the first SP2 update.

Did you check the latest version?

 

Yes, I am using SP2.1. It's only a problem with the SAM3S in my experience. I'm on another project with a SAM4E, which is working fine. I haven't tried it but I would assume all the example SAM3S projects won't build in SP2.1 either.

 

As you say above, I think a copy paste error has happened with this chip's includes. Our project uses an ASF from SP1 though (and the project builds fine using a make file a gcc-arm) so it must be something being defined in the Atmel Studio toolbox? 

Last Edited: Sun. Mar 8, 2015 - 08:20 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:

Politics :( 1563 is the correct (latest) SP2

Morten, why does this version install the buggy USB drivers version 7.0.666?  Isn't this regression, I thought it was supposed to have the latest drivers, which are now version 7.0.712. frown

 

So for those having issues with drivers, AGAIN, download them from the Gallery  https://gallery.atmel.com/Products/Details/07bf16c1-444f-4ac8-8f40-9d4005575dca

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

Last Edited: Tue. Mar 10, 2015 - 07:37 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

666 was the one that was available at the time, even with it having some minor issues. I'm working on getting a entry on the download page to the 712 build, but as per usual things are not speedy. 

:: 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

I am also getting the error Unsupported device after updating to 6.2.1563. The project was created and compiled OK with 6.2. I am using the ATSAM4S16B but it looks like the SAM4S16B define is not recognised.

I also get 311 other errors for Unknown type name 'Adc', 'Efc', etc which I presume are all related.

Does anyone know if there is work around for this or do I have to roll back Atmel Studio and hope it doesn't all completely fall apart?

Thanks

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

AdrianR wrote:

I am also getting the error Unsupported device after updating to 6.2.1563. The project was created and compiled OK with 6.2. I am using the ATSAM4S16B but it looks like the SAM4S16B define is not recognised.

I also get 311 other errors for Unknown type name 'Adc', 'Efc', etc which I presume are all related.

Does anyone know if there is work around for this or do I have to roll back Atmel Studio and hope it doesn't all completely fall apart?

Thanks

 

Fixed it. For some reason the new installation is not encoding the SAM4S16B define into __SAM4S16b__ in parts.h like the previous version did. I have now added __SAM4S16B__ to the projects Symbols sections and it builds again.

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

I'm also getting this unsupported device error with a SAM4S board. Just downloaded the latest version of Atmel Studio 6.2 with SP2. Has Atmel provided a fix for this issue? Why let users download and install a broken product? 

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

meolsen wrote:
1563 is the correct (latest) SP2

 

Is that still the case?

 

Is it now working & stable - am I safe to do the update...?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am stuck between not being able to uninstall and reinstalling Amtel Studio6.2 SP2.  I am running Windows 7 and tried the Clean Install Instructions.  Even with the registry clean and the file directories deleted, I cannot reinstall without first uninstalling. The uninstall doesn't work (how could it? everything is deleted).  There must be something hidden that prevents installation?  Does anyone have advice?  

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

"I am stuck between not being able to uninstall and reinstalling Amtel Studio6.2 SP2.  I am running Windows 7 and tried the Clean Install Instructions.  Even with the registry clean and the file directories deleted, I cannot reinstall without first uninstalling. The uninstall doesn't work (how could it? everything is deleted).  There must be something hidden that prevents installation?  Does anyone have advice?"

 

Sorry to say the last time this happened to us, after days of trying to clean up, we had to reformat and reinstall Windows to get out of that situation. I hope you have better luck.