@wanderson, I did some previous random number testing and used an SD card to capture the output, so I didn't have to dedicate a PC to the task. Would that be acceptable?

Very much so, I didn't want to restrict people to hardware they may not have, but if you have such hardware it makes it somewhat easier to test. Please post the information (and sketch used) here if you can. Thank you!

New true random number library available at: http://code.google.com/p/avr-hardware-random-number-generation/

@wanderson, have a look at the sketch here, and let me know what you think:https://github.com/JChristensen/entropyTest

I don't see anything that should interfere with the Entropy library, though my experience with using the String type on the arduino has been memory leaks, or at least behavior that made me believe memory leaks were occurring. I would be curious as to how long it would be able to run. It definitely looks like a useful way to collect data for those who are unwilling/unable to use a computer to capture the data.

Thanks for running tests!

New true random number library available at: http://code.google.com/p/avr-hardware-random-number-generation/

I have also had difficulties with Strings in the past, but there were improvements in 1.0, so I thought I'd give it another go. My expectation would be that it should be able to run pretty much indefinitely. I have two SD breakout boards, I should be able to get both going here shortly. I'll let them run for 24 hours or so, then get the data to you.

Here are the test results so far. Just a reminder, that while so far the test results have been good, this library really needs a lot more testing on a lot more chips--even chip types that have already been tested. Please consider, running an arduino overnight running this test code and capturing the output. Then email me the output or attach it to a reply to this thread along with information on the type of arduino you ran it on and the text on the arduino chip.

All of the above tests were performed on different chips. No repeated tests on the same chip, unless otherwise noted. Since test number 018 failed so spectacularly, I retested that same chip in test number 022. Tests 014 - 022, 025-026, and 034-036 were performed using arduino-tiny-0100-0013.zip from http://code.google.com/p/arduino-tiny/. Test 027 and 032 was performed using Mighty 1284P core files with the original bootloader.

New true random number library available at: http://code.google.com/p/avr-hardware-random-number-generation/

All of the above tests were performed on different chips. No repeated tests on the same chip, unless otherwise noted. Since test number 018 failed so spectacularly, I retested that same chip in test number 022. Tests 014 - 022, 025-026, 034-043, 049-053, and 056-070 were performed using arduino-tiny-0100-0013.zip from http://code.google.com/p/arduino-tiny/. Test 027, 032, 046-048, and 055 were performed using Mighty 1284P core files.

New true random number library available at: http://code.google.com/p/avr-hardware-random-number-generation/

I have also had difficulties with Strings in the past, but there were improvements in 1.0, so I thought I'd give it another go. My expectation would be that it should be able to run pretty much indefinitely.

It should run indefinitely with the String implementation (developed in Teensyduino) which I tried to contribute for Arduino 1.0. Sadly, the String that made it into Arduino has numerous changes that defeat much of the careful optimization work I did. My attempt to fix memory allocation problems was also not used.

If it crashes on an Arduino board, could you please give the same sketch a try on a Teensy?