Some Cordial Feedback on AVRFreak [WAS: Something offensive]

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

In case anybody is ATTEMPTING a transistion from ARDUINO TO AVR.. YOU WILL NOT FIND USEFUL INFORMATION ON AVRFREAKS. TRUST ME.. I TRIED. YOU ARE WASTING YOUR TIME HERE.

Quote:
You should start a new thread on LCDs and/or Arduino libraries
Well ALRIGHT.. couldnt agree with you more.. when do we start? But WAIT! Surely its been tried before? Surely.. someone has 'long since' ported those 'DREAMY' Arduino libraries (You know.. the one's that DO what theyre suppose to) over here to AVR-landia? Yes those! I mean because even if "the topic" has been stabbed at (which it has been brought to my attention, it has) where are the results? To make a point.. lets say it has been rehashed, pre-chewed, overcooked, ground down, blued, tie-dyed, humped, tatooed, pressed in a steel vise and turned into fur. Pressure cooked, pole-vaulted, ratcheted, creased, wiped-down, sling-shotted, regurgitated, re-eaten, re-structured, ostracized, shifted and finally excreted.. the results should be lying around here somewhere? right? WHERE ARE THEse libraries??? I dont see em anywhere and I looked. No seriously.. where are they?

Look.. Im new here and yes that smell "is" NOOB after-shave. As if the topic itself weren't a dead give-away. Ok, Im not proud of it.. but thats what it is. So I find that by having programmed an atmega32 and an attiny2313 by means of a homemade 'BMF' Arduino Avrsip [usb to serial cable] programmer I have inadvertently bitten the apple and traipsed onto these parcels of uglyness called timers and interrupts. These that are now (thanks to the likes of SMILEYMICROS and EXTREME ELECTRONICS tutorials) beginning to make serious sense. I mean until recently I thought that things like timers interrupts and eeprom were simple manifestations of cruelty. Things in the datasheet you dont want to know about because they lie beyond human comprehension and even the mcu designers dont know why theyre there. Well well.. so these are actually vital.. as in.. advance a counter without maiming your program because you POLLED it to death. For some reason the joke "Johnny pays a visit to the frogs".. Ok so Johnny is sitting in class.. woops nevermind.

In any event.. if anyone 'in the know' can help me translate, say, the Arduino lcd lib from cpp to c making it avr digestible I would be most grateful. From what I understand its not that easy a thing to do because of inheritance? Kripes.. what do i know? One of the things I like about the ARduino libraries is, in that they dont take up gobs of your main program space it just makes it easier to get things done. Btw.. I reserve the right to edit this post whenever I feel like it. :o) honk.

Last Edited: Sun. Aug 29, 2010 - 04:53 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Why do you talk about "Arduino land" and "AVR land". The two are EXACTLY the same thing. Arduino is simply avr-c++ being run with a main() that contains:

int main(void) {
  init_arduino_libs();
  setup(); // you provide
  while (1) {
    loop(); // you provide
  }
}

Otherwise Arduino *IS* just plain C++

If you want to use their library code in a non Arduino context then just write you main() in a .C or .cpp file rather than a .c file and it will be compiled as C++ rather than C.

But exactly what is wrong with working within the Arduino environment anyway? If they have the lib for what you are trying to achieve then write the program there.

As moderator I will just point out that this is a CROSS POST (https://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=96474&highlight=) and I already told you in a prior incarnation how to convert C++ to C. Usually I'd lock/delete a cross post but I'll let this one run but DO NOT continue this discussion in multiple threads. Either continue where this was already discussed in GCC Forum or continue with this thread but not both. When one has "gone quiet" I will lock it so no one accidentally wastes their time making replies that have already been made in the other copy (which is exactly why cross posting is not permitted).

Cliff

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

Quote:
Why do you talk about "Arduino land" and "AVR land". The two are EXACTLY the same thing. Arduino is simply avr-c++ being run with a main() that contains:
I can see I am as amazed you perceive Arduino and Avr being EXACTLY alike that, no doubt, you think I dont. Of course, you have more experience.. so who am I to argue? Ok Fine. Arduino and Avr are EXACTLY the same.. I assume you mean, because they share the same compiler right? Beyond that (as a NEW GUY) thats where the similarity ends. The ability to compile an Atmega32 (which affords me critical pin space) not to mention a "wide range" of other chips in Avrstudio nullifies any likeness between the two. The difference is not only substancial but impacting as far as Im concerned. But clearly, thats not where youre coming from.

So here I am, just off the boat, and my thoughts are well - no problem - I'll just find the necessary libraries, plug em in and keep on trucking. WRONG. Instead of spending my time coding and making these mcu's do the very cool stuff they do (which is why im here in the first place) I find myself suddenly turned detective tracking down, unpacking, installing and discerning the differing libraries particular methods of doing things. Then when those library comes up short which invariably has been the case 'so far'.. I find myself having to seek help via posts in the hope of getting results. As I mention in other --CROSSPOSTs-- while I have been able to plug in, say, an lcd library (namely: peter flurry's and Avinash Gupta's of extreme electronics libraries [whom I have nothing but respect for]) that do get letters onto your lcd, in that these do not account for the fact that my lcd is a 20x4 and not a 16x2 and in that the option is not available to "adapt" (as it is on the Arduino libraries) is a serious head-banger. And While I can take flurrys and extreme's libraries apart and make the necessary adjustments What bugs me is that such a vital parameter could be missing.

Regarding...

Quote:
As moderator I will just point out that this is a CROSS POST (https://www.avrfreaks.net/index.p...) and I already told you in a prior incarnation how to convert C++ to C. Usually I'd lock/delete a cross post but I'll let this one run but DO NOT continue this discussion in multiple threads. Either continue where this was already discussed in GCC Forum or continue with this thread but not both. When one has "gone quiet" I will lock it so no one accidentally wastes their time making replies that have already been made in the other copy (which is exactly why cross posting is not permitted).

Let me say this. My goal is to make the TRANSITION from Arduino to Avr a reality. PERIOD! Whether this TOPIC is "locked" or not is irrelevant. As long as the Arduino libraries are made accessible to avrstudio.. you can graphitti the method on a bathroom wall and Im a happy camper. By the way.. I tried your "METHOD" of removing the "::"'s and "This -->"'s to no avail. This tells me you havent tried it.. I did - doesnt work. Of course, remember, Im a NOOB and my knowledge of C (not to mention cpp) is limited at best.

For example you say get rid of the "::"'s and "this -->"'s. I have to assume you mean as JohanEkdahl puts it.. the "::"'s have to be turned into structures. Right? I havent gotten to the "this-->"'s yet.

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

how do you erase a double post?

Last Edited: Sat. Aug 28, 2010 - 05:47 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The best thing you can do for yourself if you want to learn is to DELETE everything Arduino and just use "normal" assembler or compiler (brand and language of your choice), a programmer like a AVRISP Mk2 or a Dragon or better still a JTAG Mk2. ie take off the training wheels and start pedalling, you will fall and hurt yourself a little but you learn to ride properly.

In real life jobs you will not use an Arduino and it's environment so get used to real life stuff.

Having said that I believe that the Arduino board (and other prebuilt boards) are excellent tools to get something running. But you can do a similar thing by using a STK500.

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

If you are going to do serious development work with the AVR/Arduino then you will eventually have to get used to working with precision symbols.

Start with precision English and move on to precision C. In English, the words " I'm " and " that's " and " don't " MUST have the apostrophe character in the correct position. Because they are standardized contractions of other words. If you don't use precision grammar then your human compiler audience, that is, anyone who is trying to read and make sense of your symbolic input (your verbal tantrums) is not going to be successful at understanding exactly the points that you are trying to communicate.

Human compilers of natural languages are generally able to ignore minor syntactical errors (if they know the language fluently). But don't be surprised if you find yourself spending hours trying to find out why your code won't compile and discover that it's because some line is missing a " ; " or other symbol in a key position.

Programmers who hate 'grammar nazis' are not serious people, because they don't understand the fundamental nature of the profession that they have chosen. Which is the manupulation of symbols according to precise rules.

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

Hey Simonetta: would you (or anybody else for that matter) kindly explain how to use the Arduino libraries in Avr? If you dont how.. join the club.. but please stick to the subject.

I would prefer people post who are part of the solution and not the problem. dig?

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

As the issue has been brought up a number of times I decided to do a bit of digging ( as I don't use the Arduino framework myself and didn't know the answers I wanted immediately ). First off, Cliff is entirely correct in stating that Arduino is EXACTLY the same as avr ( in so far as C++ code is concerned ). What you get with Arduino ( speaking of the entire system at the moment ) is an IDE, board and set of libraries that work together perfectly ( or as close as can be expected of any software ). The framework that I alluded to earlier, would include the hardware interface code, the standard "Arduino" libraries, and any other libraries that people have written for use with Arduinos. All of that code is standard AVR C++ code. The reason it is difficult to use the Arduino libraries with "non-Arduino" code is that the libraries are highly dependent on the lower levels of the framework. It can be said that ( putting on my Computer Science hat for a moment ), the library structure is tightly coupled within the vertical hierarchy.

So, what does that mean if we simply want to use the upper-level libraries themselves? Simple, you can't. All the standard libraries ( and therefore derivative libraries as well ) are built on the Arduino Wiring core. It is the implementation of the Wiring API ( combined with the object-oriented features of C++ ) that gives Arduino sketches their peculiar look: the use of digitalRead(...) and digitalWrite(...) in place of, eg PORTB |= 1 << 0 or values = PIND for instance, and other Wiring methods. Because the libraries are built using the Wiring API base, that base must be there for the libraries to be usable.

To that end, I did a quick survey of what is required to port the Wiring API ( and other hardware interface base functionality ) to a new processor ( board ); it isn't pretty. It is obvious that Arduino was not designed for ease of porting. That makes sense actually, as that is not its greatest strength - ease of use by beginners. Nevertheless, to use the libraries requires porting to new hardware. As might be expected, the porting required ( so far as I saw in my cursory analysis ) is limited to hardware differences. However, there is no localized hardware information file that can be updated. These seem to be the files that would require work ( all in hardware/arduino/cores/arduino/ in the source distribution ):

HardwareSerial.cpp -- USART Setup
HardwareSerial.h -- Number of USARTS
pins_arduino.c -- Pin Mapping
pins_arduino.h -- Pin Mapping
Tone.cpp -- Timer Setup
wiring.h -- ADC Reference Setup
wiring.c -- Timer Setup
wiring_analog.c -- ADC Setup
wiring_digital.c -- PWM Activity Setup
WProgram.h -- Pin Mapping

Obviously this is not a task to be taken lightly, especially as the changes are not confined to the top of the files, but are interspersed through the implementation ( the changes are mostly conditional compilations ). Also, the setup of any particular peripheral may be separated as is clearly seen with pin mappings.

It might be reasonably suggested that the Arduino project needs to rethink its porting system as, though it is working now, if there is an explosion of processor ports the system could become quite fragile; however, the current system works just fine for the project's stated objective.

Anothe minor point is that the init() and setup() functions must be called to guarantee that the core libraries are functional, ensuring ( consequently ) that the remainder of the libraries will work properly. These calls are wrapped in the Arduino framework's main.cpp and so are transparent there. It is not a major point, but it is a necessary step to get the libraries working and that's the point of the thread after all.

What it all boils down to is that this is a porting project just like any other when one wants to use a library on a processor it wasn't designed for. In this case, however, there is lots of code to port, spread all over the place, and not well documented. I see two possible options if it is absolutely required to use Arduino libraries: 1) bite the bullet and slog through a port, or 2) convince those in charge of the Arduino project that it would be a great advance to streamline porting - wait until it is implemented - then port.

We started talking about how Arduino and AVR are the same; we've come back to that now. Any library, in any language, will require porting if it is going to be used outside of its original environment. That can mean different software or different hardware, the approach is similar, but the programmer needs to decide if such work porting is justified or if another path is more appropriate.

Martin Jay McKee

As with most things in engineering, the answer is an unabashed, "It depends."

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

Hey Martin, I want to say Im very grateful for the info you posted. Based on your information and others who have taken the time to explain (in terms I dont understand yet) the nature of the beast that porting the Arduino libraries into avr would be - I get it: Its not a practical solution. So... how hard would it be to generate new libraries that borrow from established libraries (like flurry's and extreme's) and remake these in such a way they make use of Arduino commands? Take for example, the Arduino lcd library. From the very start.. you have the option of using a 4 or 8 bit lcd.

LiquidCrystal lcd(X, Y, a, b, c, d);
LiquidCrystal lcd(X, Y, a, b, c, d, e, f, g, h);

As well..

lcd.begin(x, y);

allows me a broader range of lcd's suited to my projects needs. I just dont get how flurry or extreme could have missed these must have parameters in their lcd libraries. After that, its all down hill with lcd.this and lcd.that. Are we in agreement 'easy of use' means more time perfecting what your project is actually going to do?
Anyway as far the topic of this discussion is concerned, instead of it being "porting Arduino libraries" why not call it "avr library zone" with the idea of borrowing from other libraries so as to not re-create the wheel ? Here, I think, an avr library tutorial similar to the Arduino "morse code" library tutorial would be a great way to start.

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

Dude, you have selected a problem solving strategy that won't work out.

First you invent a problem. Then you blow it out of proportion. You write endless treatise about how the imaginary problem shall be a problem. What you don't manage to write is a coherent, precise, to the point description why this is a problem and what you want.

Instead you are shouting at us and show a general disrespect for us. You don't listen to experienced people. You start at least three threads about the imaginary problem. You write more treatise about why you are right, everyone else is an idiot, has no clue, why you don't need to listen, and why you are entitled.

Dude, you have issues.

Stealing Proteus doesn't make you an engineer.

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

Quote:
you have the option of using a 4 or 8 bit lcd.
The HD44780 LCDs that the library supports do not come in 4 bit and 8 bit versions, rather they have the capability to run in 4 bit or 8 bit mode. There is absolutely no advantage to using one of these LCDs in 8 bit mode, so libraries such as Peter Fleury's find no reason to support 8 bit mode. 8 bit mode simply takes up 4 extra pins.
Quote:
while I have been able to plug in, say, an lcd library (namely: peter flurry's and Avinash Gupta's of extreme electronics libraries [whom I have nothing but respect for]) that do get letters onto your lcd, in that these do not account for the fact that my lcd is a 20x4 and not a 16x2 and in that the option is not available to "adapt"
I am not familiar with Gupta's code, but the Fleury library most certainly can handle 20x4 LCDs. In fact it can handle any LCD that the Arduino LCD library can. It can even use whatever pins and ports you want for any of the lines. The only thing that it can't do without modification is use fixed delays instead of the R/W line. Changing this is actually rather easy (mostly just changing one function). Does it have a function to call to set these parameters? No. It has parameters in the header file to set these, which has the distinct advantage in that the settings are known at compile time rather than set at runtime.

Regards,
Steve A.

The Board helps those that help themselves.

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

The irony of this is that if the sad little whinger spent even 5 minutes googling rather than spouting verbal diarrhea he would have found this:

http://www.lcd-module.com/downlo...

which has DOG-M LCD (SPI interfaced) module initialisation code in "AVR C".

Ho hum.

From that page:

// Versorgung 3,3V, 4fach-Boost an
//------------------------------------------------------------------------------
// Konstanten fr ST7565
//------------------------------------------------------------------------------

#define DISPOFF      0xAE
#define DISPON       0xAF
#define DISPSTART    0x40
#define PAGEADR      0xB0
#define COLADRL      0x00
#define COLADRH      0x10
#define ADCNORMAL    0xA0
#define ADCREVERSE   0xA1
#define COMNORMAL    0xC0
#define COMREVERSE   0xC8
#define DISPNORMAL   0xA6
#define DISPREVERSE  0xA7
#define LCDBIAS9     0xA2
#define LCDBIAS7     0xA3
#define RESET        0xE2
#define SETPOWERCTRL 0x28
#define REGRESISTOR  0x20
#define SETCONTRAST  0x81
#define STATINDMODE  0xAC
#define BOOSTERRATIO 0xF8


//------------------------------------------------------------------------------
// Portdefinitionen
//------------------------------------------------------------------------------

#define DOGCSPORT	PORTC
#define DOGCS		7

#define DOGRESPORT	PORTC
#define DOGRES		6

#define DOGA0PORT	PORTC
#define DOGA0		5

#define DOGSCLPORT	PORTB
#define DOGSCL		0

#define DOGSIPORT	PORTB
#define DOGSI		1


//------------------------------------------------------------------------------
// Makrodefinitionen
//------------------------------------------------------------------------------

#define SetBit(adr, bnr)	( (adr) |=  (1 << (bnr)) )
#define ClrBit(adr, bnr)	( (adr) &= ~(1 << (bnr)) )

#define	DOGENABLE  ClrBit(DOGCSPORT, DOGCS)
#define	DOGDISABLE SetBit(DOGCSPORT, DOGCS)

#define	DOGCOMMAND ClrBit(DOGA0PORT, DOGA0)
#define	DOGDATA    SetBit(DOGA0PORT, DOGA0)


//-----------------------------------------------------------------------------------------

void dogSPIout(char out)
{
  char msk;

  msk = 0x80;
  do
   { ClrBit(DOGSCLPORT, DOGSCL);
     if(out & msk)
        SetBit(DOGSIPORT, DOGSI);
     else
        ClrBit(DOGSIPORT, DOGSI);
     SetBit(DOGSCLPORT, DOGSCL);
     msk >>= 1;
   }
  while(msk > 0);
}

//-----------------------------------------------------------------------------------------

void initDOGM132(void)
{
  contrast = 33;
  Xpixel   = 132;
  Ypages   = 4;

  DOGENABLE;
  DOGCOMMAND;

  dogSPIout(DISPSTART + 0);
  if(topview)
   { xoffset = 0;
     dogSPIout(ADCNORMAL);
     dogSPIout(COMREVERSE);
   }
  else
   { xoffset = 0;
     dogSPIout(ADCREVERSE);
     dogSPIout(COMNORMAL);
   }
  dogSPIout(DISPNORMAL);
  dogSPIout(LCDBIAS9);
  dogSPIout(SETPOWERCTRL+7);
  dogSPIout(BOOSTERRATIO);     dogSPIout(0);
  dogSPIout(REGRESISTOR+3);
  dogSPIout(SETCONTRAST);      dogSPIout(contrast);
  dogSPIout(STATINDMODE);      dogSPIout(0);
  dogSPIout(DISPON);

  DOGDISABLE;
}

//-----------------------------------------------------------------------------------------

void initDOGM128(void)
{
  contrast = 22;
  Xpixel   = 128;
  Ypages   = 8;

  DOGENABLE;
  DOGCOMMAND;

  dogSPIout(DISPSTART + 0);
  if(topview)
   { xoffset = 4;
     dogSPIout(ADCNORMAL);
     dogSPIout(COMREVERSE);
   }
  else
   { xoffset = 0;
     dogSPIout(ADCREVERSE);
     dogSPIout(COMNORMAL);
   }
  dogSPIout(DISPNORMAL);
  dogSPIout(LCDBIAS9);
  dogSPIout(SETPOWERCTRL+7);
  dogSPIout(BOOSTERRATIO);     dogSPIout(0);
  dogSPIout(REGRESISTOR+7);
  dogSPIout(SETCONTRAST);      dogSPIout(contrast);
  dogSPIout(STATINDMODE);      dogSPIout(0);
  dogSPIout(DISPON);

  DOGDISABLE;
}

//-----------------------------------------------------------------------------------------

void initDOGL128(void)
{
  contrast = 16;
  Xpixel   = 128;
  Ypages   = 8;

  DOGENABLE;
  DOGCOMMAND;

  dogSPIout(DISPSTART + 0);
  if(topview)
   { xoffset = 4;
     dogSPIout(ADCNORMAL);
     dogSPIout(COMREVERSE);
   }
  else
   { xoffset = 0;
     dogSPIout(ADCREVERSE);
     dogSPIout(COMNORMAL);
   }
  dogSPIout(DISPNORMAL);
  dogSPIout(LCDBIAS9);
  dogSPIout(SETPOWERCTRL+7);
  dogSPIout(BOOSTERRATIO);     dogSPIout(0);
  dogSPIout(REGRESISTOR+7);
  dogSPIout(SETCONTRAST);      dogSPIout(contrast);
  dogSPIout(STATINDMODE);      dogSPIout(0);
  dogSPIout(DISPON);

  DOGDISABLE;
}

//-----------------------------------------------------------------------------------------

void ResetDOG(void)
{
  SetBit(DOGCSPORT,  DOGCS);
  SetBit(DOGSCLPORT, DOGSCL);
  SetBit(DOGSIPORT,  DOGSI);
  SetBit(DOGA0PORT,  DOGA0);

  ClrBit(DOGRESPORT,  DOGRES);
  waitus(5);
  SetBit(DOGRESPORT,  DOGRES);
}

//-----------------------------------------------------------------------------------------

void DogKontrast(void)
{
  DOGENABLE;
  DOGCOMMAND;

  dogSPIout(SETCONTRAST);
  dogSPIout(contrast);

  DOGDISABLE;
}

What's the betting he finds something more to whinge about with this solution? :lol:

PS my money is on a 12 year old judging by the childish antics.

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

But Cliff, wlewis is not using the Dog LCD, the OP of the thread that wlewis had hijacked used it. wlewis, as far as I can see, is simply using a standard HD44780 display (and is simply to lazy to read the documentation of the Fleury library to find out how to set it to 20x4).

Regards,
Steve A.

The Board helps those that help themselves.

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

Oh my apologies - because she spouts such large quantities of diarrhea I took it from the first hijacked thread that she HAD to use the Arduino lib as it was the only lib she could find to support "DogLcD". If, as you say, it's just a standard HD44780 then it actually makes the pointless whinging even more unfathomable as there's got to be 50+ different HD44780 support libs an AVR C user could use. Unbelievable.

(always assuming she manages to switch the thing on |I wonder if she'll ever manage to actually display something sensible anyway?).

By the way, if it helps. The attached are the standard avr-gcc HD44780 files that come with WinAVR that I modified to drive my own 20x4 display.

Attachment(s): 

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

Quote:
little whinger

Quote:
sad

Quote:
verbal diarrhea

Quote:
disrepect

Quote:
googling

[BS removed - remember I'm a moderator and can edit your posts]

Quote:
Dude, you have issues.
you d*** tootin i have issues.. its called trying to get my little mcu to do what I want it to.. so I have dont have to waste valuable time posting on avrfreaks.

TO Koshchi:

Quote:
I am not familiar with Gupta's code, but the Fleury library most certainly can handle 20x4 LCDs.

thanks Koschi.. this is EXACTLY the kind of information Im looking for. Im going back into fluery's to see if it can be done and how.

Also.. Im gonna "hunt" around for real time clock library. Know of one out there?

Last Edited: Sat. Aug 28, 2010 - 07:18 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

wlewis wrote:
Based on your information and others who have taken the time to explain (in terms I dont understand yet) the nature of the beast that porting the Arduino libraries into avr would be - I get it: Its not a practical solution.

Sorry but which part you don't understand?

Arduino libraries already run on AVR. Thus there is no need to port them any more.

Arduino is nothing more than a simple albeit largish hardware abstraction layer with some simple code functions to do simple stuff.

When you write "Arduino" code, you write standard C (or C++, I don't care/know), but just use some of the ready-made things from the Arduino library. That all goes through standard avr-gcc compiler and ends up as standard executable. Sure, Arduino boards come with a bootloader so you can easily program the AVR with the executable.

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

jepael.. here's a newsflash for ya: PORTING THE ARDUINO LIBRARIES INTO AVR IS NOT AN OPTION. Rather the theme shifted like 5 posts ago into DISCUSSING [take note clawson] of making flexible libraries that avr can use and actually do what theyre suppose to.

NEWSFLASH:: READ ALL ABOUT IT:: PORTING THE ARDUINO LIBRARIES INTO AVR IS NOT AN OPTION. FORGET IT. BORROWING AND IMPROVING ON PREVIOUSLY MADE LIBRARIES IS!!

Actually i was going to say "stealing" libraries making use of creative license but I smell police constable clawson and his trusty subjects lurking about. Ok Spooks.. come on out I know youre there.

Last Edited: Sat. Aug 28, 2010 - 07:41 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You spend so much time writing and so little time thinking. Consider reversing that.

Stealing Proteus doesn't make you an engineer.

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

ArnoldB.. you mean like you? Where is your solution? Oh you have a judgement call instead i see.. gee thanks but no thanks.

NEWSFLASH:: NO MORE JUDGEMENT CALLS. EITHER PUT UP OR SHUT UP.

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

Do you really think your childish style and your attempts to bully us will work?

Stealing Proteus doesn't make you an engineer.

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

Quote:
this is EXACTLY the kind of information Im looking for.
And it is EXACTLY the kind of information that you would have found if you had actually read the manual that comes with the code instead of whinging that it doesn't do what you want.
Quote:
Know of one out there?
With your attitude, do you really expect any of us to help you in this?
Quote:
here's a newsflash for ya: PORTING THE ARDUINO LIBRARIES INTO AVR IS NOT AN OPTION.
And here's a newsflash for you: ARDUINO LIBRARIES ARE ALREADY ON THE AVR. This is the point that you don't get. There is no need to port anything.
Quote:
Rather the theme shifted like 5 posts ago into DISCUSSING
At no point in this thread have you DISCUSSED anything, you've only complained.
Quote:
so I have dont have to waste valuable time posting on avrfreaks.
But you do want us to spend our valuable time on catering to an infant.
Quote:
but I smell police constable clawson
And I am beginning to smell someone being banned from these forums.

Regards,
Steve A.

The Board helps those that help themselves.

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

Hey Arnold.. you feel youre getting bullied? BULLIED? thats very interesting.. how were you threatened? What was threatened? Your image.. What? What exactly is the threat? your self worth and capabilities? Separately.. by referring to yourself as "us" you have qualified yourself as a valid spokesmen for "every single person" in the known world: You might want to rework that. If you are representing others.. be clear. Like me and so and so and so feel youre bullying us. But then were back to the missing threat. Regarding a Childish style? you call defending myself from slanderous attacks childish? Have you actually read the posts? Read clawsons posts and tell me that isnt slander. Lets see.. you have upwards of 2500 posts to your credit.. surely someone of your "CALIBER" can contribute to this thread. It dawns on me you dont understand what this thread is about.. so let me help you out.

The REVISED: mission statement of this thread is simply To make quality libraries available to the avr community. QUALITY Libraries for:

1) lcd
2) glcd
2) rtc
3) memory (sd and the like)
4) encoders
5) UART

NOT TO MENTION..

6) a wide variety of sensor's out there (a biggy)

Come to think of it: This thread has been so thoroughly "SOILED" by the pessimistic aggresive ejaculations of the likes of clawson and others (whom you no doubt identify with) that starting a new thread is starting to look like a good idea. I will give you this tho.. youre right about wasting time here answering ridiculous judgement calls. One last thing.. if you can contribute to the topic.. mister over 2500 posts.. please do so.

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

Well Koschi.. youve gone South dude. By south, I mean you have (like your peers) DETOURED from the topic and worse.. far worse.. your own system of ethics. Thats cool though, I understand and know you. You are the kind that goes with the flow or in this case.. mob. Too bad you are not the "kind" that stands their ground. The reason for this is clear.. you dont stand your ground because you not only dont know what YOUR GROUND is but you dont know WHERE IT IS. So you sheepishly back out, bend over and betray yourself. I would say you cant afford this.. the price is too high.. but its too late. I would have suggested you follow your ORIGINAL INSTINCT and contribute to the topic (which you actually did do -tho minimally- before cowering down) but I see you are not the kind to "suffer" PEER PRESSURE. Still, dont feel bad dude.. many years ago at the ripe age of maybe 8 or 9 years of age I mightve done the same thing.

Still.. consider who youre siding with.. the likes of clawson? with no sense of self? A gang of pompous aggresive slanderous pessimists with no sense of self? Lets have a look at clawsons icon.. why is a CAR on his icon??? Does this guy want us to think that because he has a picture of a car and little stars on his icon he is worthy of, say, respect? Maybe he's just saying.. like madona used to say: Im a material guy. This car is cool and therefore I am cool. Now that you know that: do as i do. Well.. I prefer to not do as clawson does or you do or anyone else does - unless its in sync with my own system of values. I prefer to not do as you Koshchi do - and submit and BEND OVER. Ouch!

Oddly enough.. arent you doing the same thing youre accusing me of: WHINING AND COMPLAINING? You used up one rather large post dedicated to nothing but complaining about things ive said and not said.

And no... I dont expect HELP (tips, advice, or anything else) from this forum. Asking for tips from this forum would be comprable to going to battle with a group of blind guys whose only weapon are what.. stolen water pistols? Im way past that.. but should know that by now. I will say this.. I did have a look at fleurys lcd lib.. and didnt see where you can adjust for rows and cols. I dont doubt its there..but its like Ive said.. in that its not obvious means more time spent researching the F* libraries and less time spent on far more important matters like robot navigation and stuff.

So whats your move now? Ban me? You say that like as if its some kind of punishment. Where is the punishment if so far the only fruit coming out of this topic has been ABSOLUTE USELESS diatribe and redundancies? Think about it dude. As far as I can tell Avrfreaks is strictly an entertainment forum. Not real. This has been proven beyond any doubt. What a loser.

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

I realize that this is probably a pointless argument, but here goes anyway. At the beginning there was talk of the inability to use the Arduino system because of hardware that is not currently supported. So, 'necessary to port Arduino to the AVR?', no - it is of course already AVR code, but 'necessary to port Arduino to a new AVR MODEL?' - yes. There seems to be confusion all around, and yes, I think much of it would 'vanish like mists in the rising of a desert sun' if there were more thought and less talk, but there it is.

Martin Jay McKee

As with most things in engineering, the answer is an unabashed, "It depends."

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

Quit yer whining, fire up your editor and port the libraries to straight C or figure out how to work the linker yourself. If you code as fast as you rant, you might even be done before the next post.

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

Anyway Koshchi.. Eventhough I suspect your injured EGO will prevent you from doing so.. I challenge you to back up what you say and indicate EXACTLY where cols and rows can be adjusted in fleurys lcd lib. I just want to see you put your money where your big mouth is. After all, you were the one that brought it up. Just know.. I wont be holding my breath. You bring home one truth; if you dont take control of your life.. others will and - in your case - have. Too bad for you dude.

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

In any case its been real.. but it hasnt been real. Catch my drift..?

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

Hey you guys.. wanna see a neat trick. Watch this.

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

Quote:
Eventhough I suspect your injured EGO
Nothing you could possibly say or do would injure my ego, it would take much more than the rantings of a child to do that.
Quote:
By south, I mean you have (like your peers) DETOURED from the topic and worse.. far worse.. your own system of ethics.
I fear that you have misconstrued my first post in this thread. It was not done to help you, it was done to show that you were wrong about the Fleury LCD library not being able to do what you want.
Quote:
I challenge you to back up what you say and indicate EXACTLY where cols and rows can be adjusted in fleurys lcd lib.
Easy enough of a challenge. Under the quite obvious heading of "Definitions for Display Size":

#define 	LCD_LINES   2
#define 	LCD_DISP_LENGTH   16

Quote:
Hey you guys.. wanna see a neat trick. Watch this
Thus proving our assertion that your behavior is juvenile (and also proving my point that you should be banned).

Regards,
Steve A.

The Board helps those that help themselves.

Last Edited: Sun. Aug 29, 2010 - 06:00 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Let me just say

Squad! Camp it up!

Stealing Proteus doesn't make you an engineer.

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

wlewis wrote:
Hey you guys.. wanna see a neat trick. Watch this.

*snore*

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

Now we all play "get the last post before the thread's locked."

Mr. Lewis, you certainly showed us.

Chuck Baird

"I wish I were dumber so I could be more certain about my opinions. It looks fun." -- Scott Adams

http://www.cbaird.org

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

Unreal. Words fail....

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

For those of you who may be unaware, this behavior started in the OPs very first posting in these forums. And apparently the OP has forgotten that I posted the very first response to his irrational ranting.

Regards,
Steve A.

The Board helps those that help themselves.

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

I always wondered how long it would take to get a big name calling session going like on sci.electronics.design.

Imagecraft compiler user

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

Thanks, Steve, for pointing out the historical precedent. That brings lots of things into perspective. I loved Arnold's "no child left behind" comment.

Chuck Baird

"I wish I were dumber so I could be more certain about my opinions. It looks fun." -- Scott Adams

http://www.cbaird.org

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

Just to note that OP's IP address was:

189.217.75.172

(Mexico in case anyone's interested)

Topic locked