Trying to burn the bootloader

[gogol]

Totally agree!  As IDE users will brick their attinies almost at 100% . An they don't understand why, because verbose output is switched off by default in the IDE.
Something I also don't like.
I would expect, to find much cleaner and better Arduino code, when people would see warnings!

I need to look to the 1.5 branch of the IDE, what they have fixed over there. 

.g

[dougal]

Ugh. I wish I had searched here earlier. I recently got a USB µISP and was trying to program a raw ATTiny85 last night. I blithely used the "Burn Bootloader" option at some point. So I guess I may have bricked that one.

Question: I'm unclear if I'm supposed to do the ISP-to-chip connections MOSI <-> MOSI and MISO <-> MISO or if I'm supposed to swap those lines. I had the impression that it's the former, though, yes?

Can anybody point me to so some clear, step-by-step instructions for programming raw chips via ISP from my Mac? Most of the tutorials I find seem to assume some prior knowledge and skip some steps, or are for setting up Arduino-as-ISP.

[DeuxVis]

In the past I have used an old AVRISP mkII, and yes the MOSI/MISO pins should be connected matching their counterpart. MOSI to MOSI, MISO to MISO.

I don't know if it's the same with your µISP, but one caveat is that you must supply power to the chip you are programming, the programmer doesn't.

[gogol]

With MOSI and MISO its different than with TX/RX.  But the names are self explaining:  Master Out Slave In  and  Master In Slave Out.
So "MO" from the Master connects to "SI" on the Slave, and "MI" from the master is connected to "SO" from the Slave.

[dougal]

Obviously, I hadn't had enough coffee when I wrote my previous post.

Oh, and just in case anyone is curious, the µISP can supply power to the chip. In fact, you can select between 3.3V, 5V, or separate power.