Show Posts
Pages: [1]
1  Products / Arduino Due / Re: New UTFT Libray with Arduino ARM spport on: February 24, 2013, 01:13:05 pm
The stuff you are looking for used to be marketed in car accessory shops for repairing rear screen heaters.
It is basically like a small bottle of nail varnish - but loaded with either silver or aluminium powder for conductivity.
You can certainly use it to fix damaged pcb tracks (remove varnish from the good area first!!) , so shorting out a couple of SM resistors should be easy.  Just don't splash it around... smiley

Graeme
2  Products / Arduino Due / Re: tinyFat Library with Due on: February 14, 2013, 04:11:24 pm
I was wondering if anyone had figured out how to use Karlsen's tinyFat and UTFT_Tinyfat librarys with the arduino due.  His UTouch and UTFT libraries work out of the box with the due and my 5.0" lcd screen but his SD card library doesn't.

I know there is an SD card library that works with the due, but I am looking to load images from the sd card and display them on the screen.

Any help would be appreciated!
Nick D.

Why not ask Henning ?  I had questions about his UTFT libraries - when used with a Mega 2560, and he answered them quite willingly once I explained what was needed. Seems a real gentleman. He may well be revamping his other work for Due applications anyway??

Graeme
3  Using Arduino / Displays / Re: Can a TFT LCD use GIF files to animate? on: January 31, 2013, 12:24:56 pm
Does anyone know how if there is a way to speed up the rendering time? Or is there another TFT available that could possibly handle multiple .raw files in a manner so quickly that it appears to be animating?

I think, having used TFT screens with a Mega 2560 and also Due, it may be possible to get simple animation using Due, even using UTFT. Not slick perhaps, but reasonable?
There are folks working on optimised 16 bit drivers for Arduino to serve specific display chipsets. These look pretty promising but may take a while until they are fully proven. The main purpose appears to be to generate 15+FPS for data displays... rather than bitmapped graphics. Have a search on the forum.

Graeme
4  Products / Arduino Due / Re: code size on: January 30, 2013, 02:32:10 am
Just to add to the confusion, here's blink with an unrolled loop - 2000*digitalWrite and delay.
Code:
/*
  Blink
  Turns on an LED on for one second, then off for one second, repeatedly.
 
  This example code is in the public domain.
 */
 
// Pin 13 has an LED connected on most Arduino boards.
// give it a name:
int led = 13;

// the setup routine runs once when you press reset:
void setup() {               
  // initialize the digital pin as an output.
  pinMode(led, OUTPUT);     
}

#define do10(x) x x x x x x x x x x
#define do50(x) do10(x) do10(x) do10(x) do10(x) do10(x)
#define do250(x) do50(x) do50(x) do50(x) do50(x) do50(x)
#define do1000(x) do250(x) do250(x) do250(x) do250(x)

// the loop routine runs over and over again forever:
void loop() {
 do1000(
  digitalWrite(led, HIGH);   // turn the LED on (HIGH is the voltage level)
  delay(1000);               // wait for a second
  digitalWrite(led, LOW);    // turn the LED off by making the voltage LOW
  delay(1000);               // wait for a second
 )
}
Code:
code size         mega    due
normal blink      1662    9740
unrolled blink    44866   41716

Due beats Mega by 3k smiley-grin

This bears out my general experience with the Due - the larger code sizes are because it has a more comprehensive runtime. Ignoring the overhead, code for code the Due seems to be slightly better than the Mega.

I reworked some of my bulkier code and compiled for both Due / Mega.   As everybody has acknowledged, there is more overhead, but there is also a lot more performance.

 #pragma message: Compiling for Arduino Due (AT91SAM3X8E)...
Binary sketch size: 62,216 bytes (of a 524,288 byte maximum)

For the Mega - compiles to:
Binary sketch size: 45,634 bytes (of a 258,048 byte maximum)

Nothing as bad as the apparent initial 6:1 sort of increase. Relax I think. smiley

I think Due will be pretty good to use, well, after I re-jig the Analog input levels and assorted 5V TTL logic level changers etc.

Graeme

5  Products / Arduino Due / Re: code size on: January 29, 2013, 11:00:42 am
Using this sketch as the blink code:

Code:
#include <FastDigitalIO.h>

void setup() {  
FastDigitalIO< 13 > p;  
 p.mode( OUTPUT );
}

// the loop routine runs over and over again forever:
void loop() {
  FastDigitalIO< 13 > p;  
  p.write( HIGH );
  delay(1000);               // wait for a second
  p.write( LOW );
  delay(1000);               // wait for a second
}

I get values like ( taken off real bare minimum, not the one I posted above ):

Quote
UNO direct IO: 706, difference 240
Mega direct IO: 898, difference 232

That sounds better.. if the basic initialisation code is a little bulky, BUT program code is then fairly efficient ,there is less to worry about than I thought. I have some code that ends up >50Kb on a Mega at the moment. Some of it won't easily transplant until libraries are sorted out, but it looks hopeful  smiley
6  Products / Arduino Due / Re: Building a CAN communication protocol interface for Arduino DUE on: January 27, 2013, 08:48:25 am
Hello that_kid. I hope your foot is doing better. Here another picture of my second DIY pseudo CAN shield and a brief comparison between the two shields:

SHIELD       ADVANTAGE             DISADVANTAGE
  #1         Compact               Prone to hot spots (soldering)
  #2         Easy-to-assemble      Bulky and messy



I think  I'll be building an interface in the near future -so will be following this thread closely.  I've messed about with CAN decoding in the past - using USB can interfaces  ( Lawicwl CanUSB), and  various monitoring / message filtering software.  I hate being locked out of my car's software, so using DUE as a smart interface makes sense.
The mixture of 11 & 29 bit messages (and several different bus speeds) makes life pretty complex, and given that vehicle manufacturers like to hide useful features.. lets hope the energy & problem solving in the Arduino community can cut through the BS  smiley
Lawicel do an AVR/CAN adapter, with some sample code available.
Also worth looking at :  http://rbei-etas.github.com/busmaster/
With some  contributions from Bosch - who started it all...  open source code on github.
looking forward to see what libraries develop!

Graeme
7  Products / Arduino Due / Re: New UTFT Libray with Arduino ARM spport on: January 22, 2013, 12:03:55 pm
Hi .

I have examples for you

Arduino DUE + 5" SSD1963 LCD 800 x 480
Speed on the OLD UTFT(mod for due) VS NEW UTFT lib

OLD ONE


NEW ONE !



This is It  !



That looks  an improvement on the original hardware & UTFT library. 

However - I'm  curious how you got round the way the fonts are stored. In normal Atmel processors the data for fonts or bitmaps is stored in flash, using pgmspace.h
No longer applicable to M3Cortex CPUs....

Are they being parked in regular RAM now?  If so - how?  normal but large arrays?

Good to see Henning burning the midnight oil   :-)

Graeme

8  Products / Arduino Due / code size on: January 21, 2013, 11:56:18 am
After a lot of messing around with different micro USB cables... it works.
 smiley-mr-green

One thing amazes me though  .. If I compile "blink" for a Mega 2560  - it generates 1662 bytes of code.

Doing the same thing for Due produces 9668 bytes of code!

Am I missing something here?  The Due only has twice as much flash memory as the Mega 2560, so it would appear that there could be BIG problems with moving over some of my bigger code (compiling to about 60-70K on the Mega currently)
Is there something hugely inefficient going on in the IDE for Due??
I thought ARM code was renowned for compact-ness    smiley-confuse

Graeme
9  Using Arduino / Installation & Troubleshooting / Re: Mega 2560 - was working - can no longer install driver?? on: May 08, 2012, 03:48:50 am
I eventually found a way round the problem. I'm still not sure why it happened, though I think it's something to do with registry key ownership / permissions on files.
I created another Admin user, and found another example of a Windows CDC driver script (nothing to do with Arduino). I modified the script with the PID / VID details for the Mega 2560. The script came from a device with it's own .sys file, so I simply pointed that at usbser.sys from the XP system files.
To my delight it went through without any more fuss. 2560 is go again  smiley-grin
A driver this simple, using the windows CDC/USB/Serial components should not be causing grief..

back to coding again smiley

Graeme
10  Using Arduino / Installation & Troubleshooting / Mega 2560 - was working - can no longer install driver?? on: May 04, 2012, 08:31:31 am
I have been using a mega 2560 from an old IBM T30 laptop - with no real problems. There were a few problems recently with up loading, so I decided to re-install the 2560 - to see if that would resolve the issues.

Despite using exactly the same method to install the driver (Windows CDC / USB driver) using the .inf on the Arduino website, it refuses to install again.
I get the option to pick the 2560, accept the whql  warning, but then it stops - with a simple "the installation  has detected an error" - " the data is not valid"  (!).
I have investigated the script, and been through all sorts of checks on registry permissions. To no avail.
How on earth do I get to use my 2560 again?  (I've checked another machine - no problem- but I want to program from the laptop!!)
Anybody seen this kind of error?
thanks,
Graeme
Pages: [1]