Hi, currently vm passes the F_CPU from boards.txt. I'll test it

Hi Tim and thanks for looking in to this.

The relevant parts of boards.txt are as follows:

attiny85.name=ATtiny85 (internal 1 MHz clock)
attiny85.bootloader.low_fuses=0x62
attiny85.bootloader.high_fuses=0xdf
attiny85.bootloader.extended_fuses=0xff
attiny85.upload.maximum_size=8192
attiny85.build.mcu=attiny85
attiny85.build.f_cpu=1000000L
attiny85.build.core=arduino:arduino
attiny85.build.variant=tiny8

attiny85-8.name=ATtiny85 (internal 8 MHz clock)
attiny85-8.bootloader.low_fuses=0xe2
attiny85-8.bootloader.high_fuses=0xdf
attiny85-8.bootloader.extended_fuses=0xff
attiny85-8.upload.maximum_size=8192
attiny85-8.build.mcu=attiny85
attiny85-8.build.f_cpu=8000000L
attiny85-8.build.core=arduino:arduino
attiny85-8.build.variant=tiny8

Which looks OK.

The (truncated due to forum post size) verbose output with a 1Mhz device selected is:

Compiling 'TinyTest' for 'ATtiny85 (internal 1 MHz clock)'
Build folder: file://C:\Users\David\AppData\Local\VMicro\Arduino\Builds\TinyTest\attiny85
SketchLibFolders
arduino\arduino-1.0.1\hardware\tools\avr\lib\gcc\avr\4.3.2\include\;
Summary: Header=1 Prototypes=4 Imports=0
C:\Users\David\Documents\Arduino\arduino-1.0.1\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mmcu=attiny85 -DF_CPU=1000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=101 -DVISUALMICRO_COMPILER_VER=1 " -I"C:\Users\David\Documents\Arduino\hardware\attiny\variants\tiny8" 


And the 8Mz version:

CCompiling 'TinyTest' for 'ATtiny85 (internal 8 MHz clock)'
Build folder: file://C:\Users\David\AppData\Local\VMicro\Arduino\Builds\TinyTest\attiny85-8
SketchLibFolders
arduino\arduino-1.0.1\hardware\tools\avr\lib\gcc\avr\4.3.2\include\;
Summary: Header=1 Prototypes=4 Imports=0
C:\Users\David\Documents\Arduino\arduino-1.0.1\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mmcu=attiny85 -DF_CPU=8000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=101 -DVISUALMICRO_COMPILER_VER=1 -

I didn't know about that option, si I'll enable it and upload from Arduino and see what happnes!

Thanks

David

Here's 1Mhz as the example:

C:\Users\David\Documents\Arduino\arduino-1.0.1\hardware\tools\avr\bin\avr-g++ -c -g -Os -Wall -fno-exceptions -ffunction-sections -fdata-sections -mmcu=attiny85 -DF_CPU=1000000L -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=101 -IC:\Users\David\Documents\Arduino\arduino-1.0.1\hardware\arduino\cores\arduino -IC:\Users\David\Documents\Arduino\hardware\attiny\variants\tiny8

Looks OK. I don't have the board here at the moment, so in the morning, I'll try a VS upload v Arduino upload for the same simple source and let you know.

The problem manifests itself in a delay() function. The silver lining was that it made me learn about Timer interrupts on the tiny device...

Are you uploading using the normal serial/usb system or are you using a programmer?

Okay when you have your arduino please switch on verbose upload in the arduino ide prior to upload. I would like to see the output from that. Thanks very much.

OK, I have tackled this in a more structured way. It is the bootloader burning from VM/VS (via Arduino as ISP) that seems to be the issue:

Burning bootloader to board 'ATtiny85 (internal 8 MHz clock)' using 'Arduino as ISP'
avrdude: please define PAGEL and BS2 signals in the configuration file for part ATtiny85
avrdude: please define PAGEL and BS2 signals in the configuration file for part ATtiny85
avr_read(): error reading address 0x0000
    read operation not supported for memory "lock"
avrdude: failed to read all of lock memory, rc=-2

And after this operation, the choice of board is unchecked (you have to trust me that it was OK before). I do have a screenshot showing this, but can't work out how to paste it into a message....

So my symptom of yesterday is explained by the facts that the chip was set to 8Mhz (and did not change), the board to 1Mhz, thus things flashed more quickly.

The workaround is straightforward and is simply to use the Arduino environment to load the bootloader.

David

Yes.

It seems to forget the board name, or curiously, builds for a different device than that which is checked. I have a screenshot of this situation as well, if I could figure out how to attach it...

It built for an 8Mhz clock when the selected board was 1Mhz.

David

This might be connected to the internal system needing to remove the dash from the real board name. If I recall this change was made not so long ago.

I have some other work to complete, hopefully in a week or so I can find time to re-test the custom boards, with dashes and also the isp program upload.

Thanks very much, I want this fixed. As soon as the Arduino "Due" work is complete I'll take a look at it. (Week or two)