Just trying to test a program for an atmega128 in avrstudio4.
Avrstudio4 does not display the upper 64K program memory.
(at least I can't find out how to do this)
AS4 has been long since archived in favor of AS7. You might want to try using that. But I wonder why you want to view the program memory?
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
I don't remember such a limitation. It's tempting to download an ancient copy of 4.19 to see what you mean!
(the simulator in AS7 is effectively a late development of Sim2 from 4.19 in fact - so it's really the same sim).
I remember AS7 being like 1GB install or something foolish like that.
I don't use it often and I don't want it on my computer.
Avrstudio4 is PERFECT for what I need.
I wanted to test some spm commands for a bootloader I am doing in an atmega128.
Everything is working perfectly EXCEPT for the upper 64K.
I know it's working because I can read the atmega128 afterwards but it would be a lot easier to and way faster to simulate first.
I've downloaded AS4 (4.19) and run the installer and my Win10 taskbar is showing an icon but it seems to have gone into "background mode" with no visible UI :-(
EDIT: retried and get the same result so I'm afraid I have to conclude that I cannot run the AS4 installer on this Win10 - ho hum.
i am using win7 x64 with:
AVR Studio 4.12.460
GUI Version 4, 12, 0, 460
Service Pack 3
AvrPluginAvrAsmObject 1, 0, 0, 43
AvrPluginavrgccplugin 1, 0, 0, 4
Stk500Dll 1, 0, 0, 58
Wow not only AS4 but an astronomically out of date version. Why on earth are you using 4.12? I forget when it happened but at some stage the ELF support in AS4 switched from 16 bit to 32 bit. I am pretty sure that occurred at AS4.13. At least get AS4.18 or AS4.19 and try that!
Like i said before it works for what I need.
I don't use it for programming, just the odd time as a simulator.
If the newer versions would display the full 128K program memory then I would install it.
But the actual issue you are reporting could very well be because of the age of the version you use. Why not try 4.19 and see? As far as I remember it was possible to have more than one version installed.
I have a 4.18 on my computer (win 7), now I can't remember what it is but something is broken in 4.19.
And when you simulate it show instructions in word, so there is no problems with a 128.
Make sure to use a newer C compiler than the org. The last winAVR 20100110 (and that make in many cases better code than newer versions).
I have a place where I started the project (mega16 later mega324) in studio 4, and I don't change compiler for something that is already in the field, when I only need small updates.
what it is but something is broken in 4.19.
But maybe in this case it doesn't?
The size difference between the version you have and 4.18/4.19 is nothing considering the capacities of hard drives in the last ten years or so.
As Sparrow has said the instructions are shown in words so you should be ok anyway.
But the size difference could be the reason to keep studio 4,
In many cases the Microsoft studio is a overkill
I always used 4.18, as something changed/broke in 4.19...
Click Link: Get Free Stock: Retire early! PM for strategy
Yup, as I say the thing "broken" in 4.19 was this...
but who knows what other deltas there were between 4.18 and 4.19, there may have been fixes worth having. (unless the whole raison d'etre was all about making it prefer Atmel Toolchain to WinAVR?)
... but it seems to have gone into "background mode" with no visible UI :-(
Mike's procedure :
... on this Win10 - ho hum.
WaaS is a WiP
Make older programs compatible with this version of Windows - Windows Help
"Dare to be naïve." - Buckminster Fuller
OK, I tried version 4.19. Everything seems to be working now.
Thanks to everyone who responded to my question.
As I say this is almost certainly to do with the 16 to 32 bit ELF switch that I believe happened at the 4.12 to 4.13 transition.
© 2018 Microchip Technology Inc.