[quote author="Simpkins"]I doubt the bootloader has been over written. It is designed so that it won't overwrite itself. Shorting the PGC and PGD pins together at power-up may bring the bootloader online.[/quote]
I'll try it again when I'm home. However, I've placed a jumper between the PGC and PGD pins and tried plugging it in. The orange light does not turn on when plugged into a USB port and the device is not detected by any of my computers. Would it work better if I used a bit of wire rather than a jumper? (My pins are located in different positions since I have a V2, but http://dangerousprototypes.com/docs/USB ... are_update shows a little piece of wire being used.) That said, my connection works, because otherwise I wouldn't have been able to flash it in the first place?
For my understanding though... what's going on here?
---
******@******:~/fw_update-master$ sudo ./fw_update -e -w -v -m all -vid 0x04D8 -pid 0xFD0B -ix [sudo] password for ******: U2IO flash erasing: DONE. U2IO id programming: DONE. U2IO eeprom programming: DONE. Value not provided for "ix".
---
My understanding: - The flash has been erased. Is that where the firmware's located? - The product/vendor ID has been set. - The eeprom has been programmed (is this where the bootloader's sitting?) - No ix provided... so no firmware was written to the 'flash' which was previously erased.
So, you're right in saying that the bootloader's still there? My question then is why won't the orange light turn on? I'll try again tonight after work...
Long story short I broke my irtoy by not specifying an -ix when updating the firmware. Can I recover from this fatal mistake?
(Note: Sorry for all the angry rants... I actually had a bit of fun and laughed while writing this... I really don't hate the world, I'm just frustrated by my unique show of stupidity today... LESSON LEARNED FOR SURE!! DO NOT CUT AND PASTE CODE FROM THE INTERNET INTO A TERMINAL WINDOW, ESPECIALLY WHEN YOU HAVE THE WORD SUDO IN THERE SOMEWHERE!!! TRUST ME... MOST STUPID IDEA EVER AND I'M LUCKY I DIDN'T BLOW UP THE NEIGHBOURHOOD WITH THIS GIVEN I DIDN'T READ THE CODE AND UNDERSTAND IT BEFORE CUTTING AND PASTING!!)
Background: My device came with version 12 of the firmware (although I bought it a couple of weeks ago... WHY?!?!) also, as soon as I got it working with my aircon (i.e. turning it on and off) it randomly went into 'dead' mode (orange light ALWAYS on.)
I'm on a Mac but use multiple linux boxes with different distros. I struggled to get the firmware flashing software to compile, let alone work...etc so stuck with version 12. When it went into dead mode I went 'meeeeh... if I flash it with the upgrade it will probably fix it, maybe the firmware's corrupt or something?' So I did that.
Steps I took to break it: 1) Put the jumper into position. 2) Compile all the software (didn't work on most of my machine blah blah blah worked on one of my Linux servers) 3) STUPIDLY just copy and paste the instructions from the internet into an ssh session... riiiiight? [lesson: never do this again, understand what you're doing and hand type what you want rather than doing a cut and stick job]
[attachment=1]
4) Get all excited and congratulate yourself on getting the flashing utility to work (when in fact you've just bricked your irtoy)
******@******:~/fw_update-master$ sudo ./fw_update -e -w -v -m all -vid 0x04D8 -pid 0xFD0B -ix [sudo] password for ******: U2IO flash erasing: DONE. U2IO id programming: DONE. U2IO eeprom programming: DONE. Value not provided for "ix".
---
So... the flash has been completely erased, the orange light doesn't turn on at all (because there's no firmware or bootloader) and my irtoy has been bricked. No new irtoys are shipping until the 31st of May so this is a big of a bummer (because I was really excited about this aircon automation project.)
Although I'm stupid and deserve to be ridiculed and punished, is there a way out of this. CAN I FIX MY UNIT??!?!
Also, like any bad workman, can I blame my tools for a moment: 1) What kind of an effing stupid script allows you to erase your device when you haven't told it to upload SOMETHING?!?!? The software allows the device to commit suicide!! WHY?!?!? I'm gonna change the logic on mine so that if there's no "ix" it doesn't just say 'Value not provided for "ix"'... it WARNS you before doing ANYTHING and rather than "ix" (WTF is that?) says 'YOU HAVEN'T TOLD US WHAT FIRMWARE YOU WANT TO UPLOAD!!!! PROCEEDING WILL BRICK YOUR DEVICE YOU FOOL!!!!'
In short, the software's not to blame, but it COULD be better.
2) Dangerous prototypes... I'm onto you for providing the WRONG code in your cut and paste. Check it out again...
NEW LINE... MAYBE THERE'S A PROMPT OR SOMETHING?!?!?!
[name of firmware]
WHY... WHYYYYYYYYYY DON'T THEY JUST PUT THEM IN THE SAME LINE SO THAT BY DEFAULT YOU WILL DO A PROPER UPGRADE?!?!? (And not have a path, the firmware's provided with the code and is in the same folder!!!)
3) Something is horribly wrong with the firmware updater. There's many versions on the forums and most can't detect the device anymore. Updates anybody?
Oh and the link to the (dud) Mac software is dead. The way back machine found it for me so I've attached it below (just so that it doesn't get lost forever.) Dud software and I'll be using Linux for all of my record and playback fun. However, it sorta works and can do things like reset the device so meh... here it is...
