Studio 7 (7.0.943) not generating output files (ELF, HEX, Etc.) even though checkboxes selected. ATtiny104_Xplained on TPI/mEDBG

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

Ladies and Gentlemen,

 

I cannot get Studio7 (v7.0.943) to generate either a .HEX file or a .ELF file at any point before, during, or after the build. I'm trying to program an ATtiny104_Xplained via TPI/mEDBG. I'm completely new to the TPI & mEDBG interface, I'm sure I'm missing something. I've spent 4 hours on this to no avail.

 

In Project ---> attiny104_test Properties ---> AVR/GNU Common ---> OutputFiles, all checkboxes are checked:

 

.hex

.lss

.eep

.srec

.usersignature

 

After building, only one file appears in the Solution Explorers "Output Files" folder, and that is "libattiny104_test.a"

 

No .HEX or .ELF file exists on my C:\ after the build. Not in the project directory. Not in Studio7 directory. Nowhere.

 

Is my necessary .ELF output file somehow embedded within this ".a" file?

 

  • I'm working with a fresh install of Studio7 on a recently "wiped" Win10 laptop. I selected only the 8-bit AVR options for the Studio7 install.
  • My device is an ATtiny104_XPLAINED, to which I can successfully connect to the AtTiny104 via TPI on mEDBG.

 

Probably doesn't matter, but I'm successfully connected to the device because I'm able to:

 

  • Read the Device Signature and the Voltage with the Device Programming dialog box.
  • Successfully read the flash memory into a .HEX file FROM the chip
  • Successfully erase the device (Erasing device... OK)

 


Build Output:

------ Build started: Project: attiny104_test, Configuration: Debug AVR ------
Build started.
Project "attiny104_test.cproj" (default targets):
Target "PreBuildEvent" skipped, due to false condition; ('$(PreBuildEvent)'!='') was evaluated as (''!='').
Target "CoreBuild" in file "C:\Program Files (x86)\Atmel\Studio\7.0\Vs\Compiler.targets" from project "C:\Users\Justin Hays\Documents\Embedded Programming\attiny104_test\attiny104_test\attiny104_test.cproj" (target "Build" depends on it):
    Task "RunCompilerTask"
        Shell Utils Path C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils
        C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils\make.exe all --jobs 2 --output-sync
        make: Nothing to be done for 'all'.
    Done executing task "RunCompilerTask".
    Task "RunOutputFileVerifyTask"
    Done executing task "RunOutputFileVerifyTask".
Done building target "CoreBuild" in project "attiny104_test.cproj".
Target "PostBuildEvent" skipped, due to false condition; ('$(PostBuildEvent)' != '') was evaluated as ('' != '').
Target "Build" in file "C:\Program Files (x86)\Atmel\Studio\7.0\Vs\Avr.common.targets" from project "C:\Users\Justin Hays\Documents\Embedded Programming\attiny104_test\attiny104_test\attiny104_test.cproj" (entry point):
Done building target "Build" in project "attiny104_test.cproj".
Done building project "attiny104_test.cproj".

Build succeeded.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========

 


#include <avr/io.h>

int myfunc(void)
{
	DDRA|=(1<<PA7);
	while(1)
	{
		PORTA|=(1<<PA7);
		PORTA&=(1<<PA7);
	}
}

 

This topic has a solution.

Last Edited: Sat. Jun 11, 2016 - 10:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think you have chosen a library project instead of a executable project.

 

See here

:: Morten

 

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

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen, that's exactly what happened. Mis-clicked when I first created the project...how dumb of me no

 

The solution is: When creating a new Studio project, if you accidentally select "GCC Static Library Project" instead of "GCC C Executable Project", you're probably not going to get output files such as .ELF, .HEX, etc.

 


 

I guess I'll leave the thread un-deleted in case someone else experiences the same problem - mod's kill it if you wish...

Last Edited: Sat. Jun 11, 2016 - 10:37 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Of course mods won't kill it. Somebody's likely to have the same problem and the answer is right here for them.

 

277,232,917 -1 The largest known Mersenne Prime

Measure twice, cry, go back to the hardware store

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

Thank you so much for answering this question.  It is exactly what I was doing!!  Doh!!

Andrew