Another Studio 7 Problem??

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

I imported a Studio 6 project to Studio 7 and got it running.

 

All was working fine until I tried adding a new file to the project.

 

Solution Explorer knows the file is there. I can edit the file.

 

But when I build the project the new file IS NOT included.

 

I have spent several hours on this problem. I have tried removing the file and recreating it. NO LUCK!

 

Any suggestions?

 

Bob Macklin

Seattle, Wa

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

How did you "add" the file?

 

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

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

I right clicked on the Project in Solution Explorer, them selected "Add".

 

Then I selected add an assembly file.

 

It created the .asm file. I can open and edit the file from Solution Explorer.

 

I have done this many times using Studio6 (and earlier)

 

I've also done this with Studio 7 when I was using C++..

 

Bob Macklin

Seattle, Wa

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

Isn't .asm a avrasm2 file? I guess you're writing for GAS? In which case the file should be .S

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

This is a program started many years ago with probably Studio 4 in assembly language. It worked well all the way through Studio 6.

 

I have been doing assembly language programming since about 1970.

 

All the other files in this project are ".asm" files.This ",asm" file was created by Solution Explorer.

 

Bob Macklin

Seattle Wa

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

So, is the action of the file Compile? (right click the file and go to its properties)

 

Also, post the build output and the name of the file you're not getting compiled...

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

It'a *all* asm files?  The Atmel assembler does not produce "linkable" object files from .asm, so on a pure asm project you have to have some other way of combining multiple files (which I don't know, off the top of my head, other than perhaps a "main.asm" that does a bunch of ".include "asmfile1.asm"" statements.)  Also, you can't link files assembled with the Atmel Assembler to C or C++ code.

 

(Yes, this makes the Atmel assembler different, and pretty "weak", compared to the assemblers that have been available for other CPUs since the 70s.  I guess the Atmel folk are/were pretty much HLL afficionados from the start.)

 

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

The properties for this file do say "COMPILE".

 

This project is many ".asm" files. The assembler does assemble all of them (except this one) and links them to an executable file.

 

Bob Macklin

Seattle, Wa

 

 

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

Dumb question....

 

In your main entry file, did you add an include to it for the new file?

 

Dumb question I know, but hey, ya never know....

 

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

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"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, RSLogix user

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

The missing "INCLUDE" statement was the problem.

 

All is fixed now .

 

Thanks,

Bob Macklin

Seattle, Wa

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

cklinbob wrote:

The missing "INCLUDE" statement was the problem.

 

All is fixed now .

 

NICE!!  Good going!

 

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

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"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, RSLogix user

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

When you have been away from this kind of thing for a couple of years there are a lot of things you forget about!

 

And "C" programming habits don't work well on ASSEMBLY language programs!

 

Bob Macklin

Seattle, Wa

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

And "C" programming habits don't work well on ASSEMBLY language programs!

Meh.  It depends on the assembler.  One of the problems with the current HLL focus is that the whole assembler ecosystem ("industry standard" macros, linkers, libraries, etc) that used to be pretty substantial back in the 80s has become ... neglected.  If you want to program an ARM in assembly language, you probably have to put up with a tool that doesn't quite match the published syntax, and have to start out by converting C .h files (or some sort of XML) to the assembly language syntax...   Hmmph.