Atmel Studio 7.0 Beta

Go To Last Post
301 posts / 0 new

Pages

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

How in the world can a video driver stop debugging... but it did and debug now seems to work. smiley

 

Thanks to Partha and Morten. yesyes

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

clawson wrote:

@pitchumani, you appear to be working for Atmel on the AVR8 toolchain - right? You really need to look at the detail I just added to that other thread.

 

It is due to the incorrect eeprom.h that is gone to packs. Morten fixed it.

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

Updated packs and did a bit more playing with the debugger. The simulator seems to work ok, I'm able to put breakpoints and run the program.

 

However using the Atmel Ice for debugging (PDI @ 1MHz with Xmega32E5) I get the following after a few seconds

 

 

EDIT the PDI clock reverts to 4MHz after setting it to 1MHz, saving the settings and reopening the project properties.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Tue. Jul 14, 2015 - 09:57 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just installed 7 Beta on Windows 7.1 and during install I selected all the packs. (default)

I am getting the same error as shown in post #35 - No devices listed.

 

What was the solution to that?

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

Probably (hopefully) post #49

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

 

meolsen wrote:

Probably (hopefully) post #49

Thank you. I did that, and a large list of packs and parts now appears in Pack Manager, but I still cannot select any part, and cannot import a project from AS6 which targets the ATMEGA328P.

 

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

Spoke too soon, sorry. I quit and re-launched AS7_Beta after doing the cache refresh and the devices are all available now.

Thanks again!

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

Yeah, that a restart of studio is needed is not obvious in the beta (we have added some notes about it).

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Thanks - I'm a happy camper now.

Looking forward to giving AS7 a run through tomorrow.

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

My C projects load and compile fine, however, the version 6.2 assembly projects load but can't compile because the path for the part include file ( such as m1284Pdef.inc ) can't be found. I can create a new 7.0 project and move all the files over to the new project and all is fine. Is there a way to more simply import 6.2 assembly projects?

 

 

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

Works OK here. Please note that I disable the automatic inclusion of .inc files so that I can control the listing output.

But then again I think I created a new project for this, can't remember. I don't have any AS6 projects on this computer as it is only installed on the laptop.

 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

But I discovered another bug or 2, PORTA and PORTB do not expand in the simulator, also GPIOR0-GPIOR2 are not visible at all.

 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

And a couple more things: Regarding post 154 above https://www.avrfreaks.net/comment... I have done another test and doing "Start debug and break" loads the code into the chip and starts running by itself (doesn't break) .

 

Also on exiting AS7 is likely to leave a messy screen, I have noticed this a couple of times. (see black line)

 

 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

If I include the full path in the main file or paste it into the toochain paths under project properties it works. -> .include "\atmel\studio\7.0\packs\atmel\atmega_dfp\1.0.68\avrasm\inc\m1284Pdef.inc"

 

I imported a version 4 assembler project and it compiles fine.

 

Modifying the path works but it's still not like a correct 7.0 project such as the 'imported' version 4 or a new created project with 7.0.

The version 6.2 projects when loaded show a blank in the items field of the new 'components' tab under project properties, there are some other differences as well.

I think the best way so far is to create a new 7.0 and move the files over.

 

 

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

Can we get some more information on Windows 10 support? It's definitely being released at the end of this month and looks like it's shaping up to be pretty great, Microsoft are definitely motivated into getting as many people on-board as possible which is great from a "reducing fragmentation" standpoint.
Currently the AS7 Beta installer won't let you progress with Win10 Insider Preview - could we perhaps get a "this version of Windows is not supported, continue anyway" message so people can still test? (There was mention early of shell things broken, anyone want to elaborate?)

 

 

On another note, the number of luddites whinging about their Windows XP installs, how bloated the new releases are and referring to Microsoft as M$ is rather depressing. Surely there's some irony in whinging about bloat and then using a full-blown IDE then feeling trapped into Windows.

 

Rather off topic, but somewhat related, are there any online AVR toolchain/editor combos?

 

Edit: The TH1 10240 (10240 = 10*2^10, very Windows 10 themed, they sure do like the number 10 a lot :P) release of the Win10 Insider Preview was just pushed out, with many sources claiming this to be the RTM version, so I doubt there's going to be any fundamental/breaking changes that would set-back progress on supporting Win10 in AS7.

Last Edited: Thu. Jul 16, 2015 - 04:16 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I just moved over an AS6.1 ASM project to this computer and opened it with AS7, it did the import and just worked. The code is just over 7K.

 

Can you show how the start up of your code looks like? Are you allowing AS& to add the .inc file automatically? You can disable this from here

just delete the .inc file

 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

 

As you can see there are NO paths generated from loading a 6.2 assembler project. There should be since a loaded version 4 project adds the paths and works and looks correct.

Yes, I have deleted the ($includeFile) and also added the paths and then used the m1284P.inc file in either the include file location or in the startup file.

This all works, however the loaded 6.2 project is not quite right, for example the components selection as you can see above does not have any information in the ITEMS field.

There are other differences also, so I don't really trust just adding the missing paths since there are some differences with a true project file that is created by 7.0

 

EDIT: Just for kicks, I created a new assembler project in 6.2 and then when I opened it in 7.0 it prompted me about upgrading the project to 7.0 and this worked fine.

I have not been prompted before when loading my assembler 6.2 projects which were originally version 4 projects but were upgraded to 6.2 projects.

Not sure why this is making a difference??

 

 

Last Edited: Thu. Jul 16, 2015 - 05:23 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This one is now bug AVRSV-6740.

 

Looks like we actually overlooked that field in the 6 to 7 project migration :S

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

John, this is not a bug. The only thing that means is that we haven't defined any bitfields inside the register. However, if you look in the bottom part of the IO view (which is hidden and non scrollable to... Let's call that one AVRSV-6741).

 

 

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Last Edited: Thu. Jul 16, 2015 - 06:21 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

That sounds like your new graphics driver :) 

 

Have never seen such a thing, so not really sure what is going on with it. Looks like something the window manager could leave behind... 

 

Re #154, it seems to have slipped past me. I'll need to see if it is reproduceable here, however it does look that things are 'working' in the sense that it is actually doing something. That message basically means that we have released the reset on the device but it haven't started to run within a given time, causing us to bail out. (Tracked internally in AVRSV-6742).

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Last Edited: Thu. Jul 16, 2015 - 06:07 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

This one is now bug AVRSV-6740.

 

Looks like we actually overlooked that field in the 6 to 7 project migration :S

 

Just to verify, as a test I created a new project in 6.2 and it gets 'prompted' for upgrade in 7.0 and all is perfect.

But 6.2 projects that were created by importing 4.18 projects do NOT get 'prompted' and ask for upgrade to 7.0, they just load straight in and the problems begin.

 

 

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

Thanks, I have updated the case...

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Last Edited: Thu. Jul 16, 2015 - 08:34 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

if you look in the bottom part of the IO view

Ok, not as nice as AS3 or AS4 me thinks... but I can live with that. cheeky In previous versions one could expand one or more ports. The same seems to happen if one presses CTRL + mouse click to select more than one port as per Windows file select.

 

That sounds like your new graphics driver :) 

But it doesn't happen with any other program so I can only blame AS7 wink

 

it haven't started to run within a given time, causing us to bail out.

The program runs for several seconds before the "bail out". By the way I'm using the Xmega E5 Xplained board for the test.

 

If and when I get a bit more time I will try a JTAG Mk3 with the same set up.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Ok, not as nice as AS3 or AS4 me thinks... but I can live with that. cheeky In previous versions one could expand one or more ports. The same seems to happen if one presses CTRL + mouse click to select more than one port as per Windows file select.

You can that for registers with defined bits (it's the hierarchy used in the device descriptor). However not all registers defines bitfields, especially not on for instance PORT registers where the whole port is used. 

 

As I said, I have added an improvement request to at least make it obvious that the window consist of a top and a bottom :)

 

But it doesn't happen with any other program so I can only blame AS7 wink

Touché

 

The program runs for several seconds before the "bail out". By the way I'm using the Xmega E5 Xplained board for the test.

It does sound strange, since we have validated with the 32E5 as well (just double checked). I have a bug internally on that we'll look into.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Hallo everyone :))

 

Can sameone test the Busy Problem with AVRISP MK2 In the new ATMEL Studio Version 7 ?

 

Thanks a lot.

 

Rolf

Windows 10 Home 64Bit, ASUS M4A89GTD-PRO/USB3, AMD Phenom II X6 1055T, Ram 2x 4GB, SSD Samsung EVO840 250GB, SATA HD 2.0TB, NVIDIA GeForce GTX 750

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

Hi Rolf,

 

I haven't tried AS7 yet, but have you seen the updates usb drivers on the Atmel website (version .888 updated in july 2015) ?

I have installed them, but I haven't tested them yet with AS6.2. Maybe you could try them out ?

Have a nice day,
Kraal

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

The busy problem is not related to the drivers, but to Atmel Studio. As far as I know the issue is fixed in 7.0 Beta.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Ah good to know... what was the point of the new drivers ? A changelog or release note would have been good...

Have a nice day,
Kraal

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

Hmh, weird that that has fallen out from that site... It is listed (slightly broken formatting) on the gallery page:

Installs USB drivers for Atmel and Segger tools for use with Atmel Studio.

7.0.888: Fixes installer issues with firmware upgrade of Xplained Mini boards.

7.0.712: Fixes installer issues due to locked system dlls.

7.0.687: Fixes issues with libusb0 on 64 bit windows [AVRSV-6132].

7.0.666: Fixes atbackend errors (missing wdapi and libusb0 dlls).

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Last Edited: Thu. Jul 16, 2015 - 01:17 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Morten!

Have a nice day,
Kraal

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

So I tried the JTAG Mk3, it will not upgrade, I think I posted the same elsewhere.

 

 

After following the above it gives a "successful" but untrue upgrade message. Trying to debug again I get

 

 

A tool IS selected as shown but not detected, in fact by closing the above window and looking at the project setting no tool is available until Studio is restarted and we go back to the beginning trying to update the JTAG which still has firmware 2.15

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

And again I try a manual upgrade but the same issue as in post 125 https://www.avrfreaks.net/comment...

 

 

the tool IS found but then it's not found??

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Copied the firmware upgrade file to the laptop with 6.1 and manually upgraded the JTAGmk3, firmware on tool now 3.2a confirmed on this computer. Still refuses to play ball in debug mode.

However programming works OK with PDI clock at 1MHz.

 

So went back to debug mode and changed the PDI clock at 1MHz. This time it downloaded the code and started to run ie it behaved like the Atmel ICE above complete with timeout errors etc. https://www.avrfreaks.net/comment...

 

Is 4MHz REALLY a safe PDI clock as shown on the debug window?? The chip is only running at 2 MHz!

 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Sat. Jul 18, 2015 - 02:11 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Got debugging "working", happy like a pig in whatever....

 

SUT 64ms creates the problem above, just got some new boards off production and tried debug and it worked! Then I started changing the fuses one at a time and it seems like it all works (Atmel Ice and Jtag mk3) with SUT of 0 and 4ms but stops working with 64ms, tried a couple of times.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Repeated test with the 32E5 Xplain board at the same thing happens, OK with SUT 0 and 4 ms, crashes with SUT 64ms.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Hi John, 

 

that sounds mighty odd... Would point towards some marginally timekeeping on our end though. Thanks for digging :)

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

By the way the Launch failed message ( https://www.avrfreaks.net/comment... ) pops up after about 15 seconds of doing a Start debug and break.

 

When I start debug the code is downloaded into the chip and it starts to run immediately ( no break) and after about 15 seconds the message comes on.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Regarding the 'PACKS', what is the difference between the file suffix .atpack and .pack?

 

I installed a newer version ATmega_DFP .atpack version 1.0.70 (i had version 1.0.68 .pack) and it installed fine but left in the old version .pack, is this correct?

 

My assembly project wouldn't compile after I deleted the old pack version because there was not a path pointing to the new pack directory located in project properties. It will add in the correct path but only when you start a new project. I added the path manually, but it seems like this should be done when you refresh or reset the cache. Or did I do something wrong??

 

 

 

 

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

Re the difference in name, .pack is the Keil one, atpack is our. atpacks are compatible with pack, but contains more information (and other architectures, .pack is ONLY ARM, while atpack can be AVR8 and AVR32 as well).

 

The component paths will not 'upgrade' by default, but they can be upgraded manually in the Project properties. Go to Project Properties|Components. Here, all the dependencies are listed. 

 

Just tested on my internal build, and there I a message when I open the project after I deleted that pack that the device is unknown, and I'm told to change it... Might be a more recent fix than the beta.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

I tried to edit the path but it won't accept the change when I just modify the 68 to 70 such as the existing path -> $(PackRepoDir)\atmel\ATmega_DFP\1.0.68\avrasm\inc

It doesn't like the $(PackRepoDir) shortcut, so I have to enter the full path before it will accept it. Just curious, is there a way to make it use the shortcut?

Last Edited: Fri. Jul 24, 2015 - 05:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

And you can't go to 'Components' and change the version there?

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

That worked! But I had to select 'use latest version of component', the 'use specific version' only shows 1.0.0 as a choice?

 

Now using that setting will always use the most recently installed version.

It seems like that should have been the default? or not..

 

Thanks for the info..version 7.0 has not crashed on my system so far, in the same time frame 6.2 would have crashed about a dozen times. good work!

 

 

 

 

 

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

The feedback is noted :) 

 

Also, the version here is a bit misleading, it is not the pack version but it's the component version. (A pack contains a set of devices and a set of components, where components are 'stuff' like headers, inc files, linker scripts, c/cpp/asm templates etc etc etc). So, the version you selected there is the version of the component (the asm project component), not the pack version.

 

The only reason why 'use latest' worked is that it basically flushes all the components out of the project, then re-adds them from the latest version from the latest pack that makes it available. At least on my machine, I got told that the device was now unknown to studio, so I needed to change it to something else if I wanted to load the project. The act of changing the device of course is is the same as 'use latest', as it needs to re-add the components for the new device. This seems to be functionality that got implemented after we released the beta.

 

Since this is a brand spanking new way for us to handle devices, we are/were expecting there to be some kinks, so good to get it out now rather than later :)

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

That makes sense. When I check for updates it shows 7.0.305 is there going to be a newer beta version?

 

 

 

 

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

Maybe :) 

 

We're in the middle of vacation time in Norway, so we're just scratching on for a couple of weeks more before we can sum up where we are and see if we need more.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Last Edited: Fri. Jul 24, 2015 - 07:48 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So, thought that I would stir up some more activity here now, by summing up the issue state that I have noted down from this thread. Scream out if I have missed anything :)

 

AVRSV-6674 Check for updates shows wrong info 

Fixed.

 

AVRSV-6675 Infinite device-selection loop if no device is installed

Fixed.

 

AVRSV-6676 Launching debug session does nothing

Documented as known issue, problem stems from 'something' in some versions of the Intel VGA driver.

 

AVRSV-6677 Issues with the graphics driver can cause rendering glitches

Documented as known issue.

 

AVRSV-6686 DFU Reports wrong JTAG ID

Fixed.

 

AVRSV-6690 Exception in tool information when using JTAG

Fixed.

 

AVRSV-6701 Display leading 0 in firmware versions

Fixed.

 

AVRSV-6732 eeprom.h and other avr-libc headers are available from too many places

Fixed. New packs are available in a linked thread a couple of pages back.

 

AVRSV-6740 Importing Atmel Studio 6.2 assembler project causes path to inc file to be wrong

Fixed.

 

AVRSV-6741 No scrolling between top and bottom half of IO view can cause bottom half to be hidden

Not started. Not a high priority.

 

AVRSV-6768 Launching on ATxmega32E5 times out when the SUT fuse is set to 64ms

Fixed.

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Morten,

 

Something that bit me in AS7 when I was trying to test an idea the other day was the internal SRAM view in the simulator. Say you pick a device that has RAM ending at 0x45F then as you page down through the IRAM you will reach a point that is "beyond" the installed RAM so that instead of showing FF the bytes show as ??. Once you reach there it seems like it behaves like the scroll down page is held down and just keeps showing you page after page of ??'s without responding to user input any more. Each time I had to use Task Manager to kill AS7. On restart I found several times that if I clicked the Start/Break icon I just got a message box to say "Command is not enabled". When it did work any attempt to repeat this always crashed in the same way.

 

Oh and another thing - how on earth do you tell what version of avr-gcc you are using from inside AS7? It seems the 8bit toolchain (and presumably 32 bit and arm too) version numbers are no longer available in the Help-About dialog because if of the way you are now repackaging and delivering toolchains.

Last Edited: Tue. Jul 28, 2015 - 08:34 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

AVRSV-6768 Launching on ATxmega32E5 times out when the SUT fuse is set to 64ms

Have you also tried with additional clock cycles at start up? I'm using around 2000 cycles + 64ms so I guess the timeout should be long enough for the highest number of cycles plus the longest SUT. Been too busy to play more with the debugger.

 

On a positive note I have programmed around 100 Xmega32E5 with AS7 and JTAG Mk3 and it went reasonably smooth. On some boards there was some over spray conformal coating on the PDI connector and it was causing strange things like a flash on the programming screen but nothing else, no error message or anything. Once the connectors were cleaned it all worked well.

 

One good thing is that the programmer picked up 5V on the target on a couple of boards which were assembled wrong by the board house and refused to program the chip. I hope they were not damaged, I'll know once I get the boards back.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly