Digispark ATtiny85 Error Loading/Parsing "hex" File

[qdenop]

Hello, I purchased Digispark Attiny85 today to use it, but I am getting an error;

Device has firmware version 1.6
Available space for user applications: 6012 bytes
Suggested sleep time between sending pages: 8ms
Whole page count: 94 page size: 64
Erase function sleep duration: 752ms
Error opening PALA\AppData\Local\arduino\sketches\BB8EBE1A9C085F37BB2769CEB2EDA794/code.ino.hex: No such file or directory
Error loading or parsing hex file.
Failed uploading: uploading error: exit status 1

---

Also, don't mind that the issue is IDE 1 x, I tried 2 x but it didn't work. I'm open to your solutions for both.

---

What should I do about this issue? I've done a lot of research. Even though there are many people asking this question, I still can't figure it out. Please help me.

[ptillisch]

Hi @qdenop. I'm going to ask you to provide the full verbose output from an upload attempt.

---

This procedure is not intended to solve the problem. The purpose is to gather more information.

---

Please do this:

1. Select File > Preferences... (or Arduino > Settings... for macOS users) from the Arduino IDE menus.
   The "Preferences" dialog will open.
2. Uncheck the box next to "Show verbose output during: ☑ compilation" in the "Preferences" dialog.
3. Check the box next to "Show verbose output during: ☐ upload".
4. Click the "OK" button.
   The "Preferences" dialog will close.
5. Attempt an upload, as you did before.
6. After the upload fails, you'll see a button on the right side of the orange bar in Arduino IDE: Copy error messages. Click that button.
   This copies the full output to the clipboard.
7. Open a forum reply here by clicking the "Reply" button.
8. Click the <CODE/> icon on the post composer toolbar.
   This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
   
   
9. Press the Ctrl+V keyboard shortcut (Command+V for macOS users).
   This will paste the error output from the upload into the code block.
10. Move the cursor outside of the code block markup before you add any additional text to your reply.
11. Click the "Reply" button to post the output.