Error 1, please explane

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

As newbie you get error messages.
Thats no big deal, but understanding them is harder.
The attachment contains the problem.
Please help me out.

 

 

Attachment(s): 

People rather die than think; and that will happen.

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

Clearly it's your use of spaces in the name. See how it's flagged "first", "project" and so on from "my first project..." 

 

Start again but this time just call it "first_project" 

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

 

Is that the AVR Plugin for Eclipse? It looks like a known issue: #65 Build fails if project name include a space.

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

Well, well, so much for the tutorial I've used.
But it strikes me as very strange that the project name is used as a file name in the make process.
Anyway I have to get used to it.

 

People rather die than think; and that will happen.

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

To be honest this looks like it could be an error in Eclipse. Note that when it invokes avr-gcc it quite rightly uses:

 

-o "My First AVR Project.elf"

 

Because of the quotes that would have worked. They correctly wrapped the target in "" so that it is seen as "one thing". The command fell down because they also passed:

 

-Wl,-Map,My First AVR Project.map

 

That would have worked if they had quoted it:

 

-Wl,-Map,"My First AVR Project.map"

 

The error appears to be that they didn't use quotes here.

 

But years of using IDEs, Makefiles and compilers tells me: never use a space or other "punctuation symbol" (including any non-ASCII character such as ÁÇÜ...) in file/project names. If you want "multi-word" then use '-' or '_' as word separators: "my_first_AVR_project" etc.

so much for the tutorial I've used.

That's kind of the issue with the internet and "everything at hand". In the old days the way you learned things was from books. Anyone who wrote a book was an expert and spent ages researching it then proof readers the the publishers pointed out typographical errors and so on. On the whole you couldn't go wrong - a book told you good stuff. The internet is different. You cannot know the provenance of what you read. It could be a work of utter genius written by a total expert or it could be a steaming pile of poo written by someone who only learned to crawl last Wednesday. Experienced readers can spot one ("MrLCD"!) from the other. Sadly it is beginners who are lead astray by any such nonsense.

 

Of course the author of your tutorial could have been quite right. Presumably if he suggested "My First Project" then he had worked through it if only to take the screen shots? So maybe his version of Eclipse was different (or differently configured) to yours?

Last Edited: Mon. Apr 27, 2015 - 09:16 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Clawson,
Thanks for the explanation.

People rather die than think; and that will happen.

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

clawson wrote:
But years of using IDEs, Makefiles and compilers tells me: never use a space or other "punctuation symbol" (including any non-ASCII character such as ÁÇÜ...) in file/project names.

Absolutely!

 

And that also applies to folder/directory names.

 

Note also that the ampersand, '&' and comma are special symbols on Microsoft (Windows/DOS) systems - so also avoid them.

 

Sure, they can all be quoted/escaped - but, as this thread shows, the chances of getting it wrong are just too high!

 

Summary: Just don't do it - then you know you'll be safe!

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

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

Why the cross post?

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

Just for cross-reference - and emphasising that it's such a common issue.

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

 ... and only 2 days before the next one came along: https://www.avrfreaks.net/forum/a...

 

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

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