I am starting this as I can not find one in the forums. Then the bootloader threads appeared below.
Need Preface, I/F platforms, burn/destination platform, general hardware.
I searched for 'boot' in the forum and nothing came up.
I have an Uno R3 setup with a protoboard shield for the Digistump bootloader burn process.
I had to reburn 2 a number of years ago and was able to resurrect 2 bricked Digistumps before.
From yesterday:
Is this relevant?
TinyCore does not support the Digistump as far as I know.
See post #6.
Which version this TinyCore? I ave already installed 0.3.0 which does not support ATtiny85 (Micronnucleus / Digispark). I have read in README file that the current version supports Micronucleus/Digispark. I ave wanted to test te board; unfortunately, I cna't include te zip file in my IDE.
TinyCore now supports the Digispark! TinyCore 0.8.0 adds support for this.
From the announcement post:
TinyCore now support the Micronucleus bootloader. This means that you can now use TinyCore to upload sketches to your ATtiny85 based Digispark or your ATtiny88 based MH-tiny board using the on-board USB connector. TinyCore also bundles the most recent version of the Micronucleus bootloader in case you want to burn the Micronucleus bootloader to one of these boards.
I have read in README file that the current version supports Micronucleus/Digispark. I ave wanted to test te board; unfortunately, I cna't include te zip file in my IDE.
Use the boards manager. If you don't, you don't get Avrdude v8.1, which is required to upload to a bard running the Micronucleus bootloader (Digispark).
This is from GitHub repository:
TinyCore --
So you're telling us that with Tinycore github process we can burn bootloader to digistump connected where?
I have an UNO r3 as an ISP with a protoboard wired as the SPI programmer.
And running the bootloader will use the UNO r3 as the programmer to burn the BL onto the digistump?
I have two stumps that run their flashed sketch but I cannot burn the bootloader with the ISP setup in the arduino docs or the tinycore
Yes. When the bootloader is corrupted the stump doesnt get recognized in the USB port.
This is what happened before on a Windows 10 machine. I was able to reburn the stump using the setup I have now.
"C:\Users\phyzx\AppData\Local\Arduino15\packages\arduino\tools\avrdude\8.0.0-arduino1/bin/avrdude" "-CC:\Users\phyzx\AppData\Local\Arduino15\packages\arduino\tools\avrdude\8.0.0-arduino1/etc/avrdude.conf" -v -patmega328p -cstk500v1 -PCOM4 -b19200 -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xFF:m
Avrdude version 8.0-arduino.1
Copyright see https://github.com/avrdudes/avrdude/blob/main/AUTHORS
System wide configuration file is C:\Users\phyzx\AppData\Local\Arduino15\packages\arduino\tools\avrdude\8.0.0-arduino1\etc\avrdude.conf
Warning: avr_mem_order[] does not know eeprom; add to array and recompile
Error: unable to locate AVR32DB48's eeprom in multi-memory address space
Warning: revise fileio_mem_offset(), avrdude.conf entry or memory type assignment [C:\Users\phyzx\AppData\Local\Arduino15\packages\arduino\tools\avrdude\8.0.0-arduino1\etc\avrdude.conf:21420]
Using port : COM4
Using programmer : stk500v1
Setting baud rate : 19200
AVR part : ATmega328P
Programming modes : SPM, ISP, HVPP, debugWIRE
Programmer type : STK500
Description : Atmel STK500 v1
HW Version : 2
FW Version : 1.18
Topcard : Unknown
Vtarget : 0.0 V
Varef : 0.0 V
Oscillator : Off
SCK period : 0.0 us
XTAL frequency : 7.372800 MHz
AVR device initialized and ready to accept instructions
Device signature = 1E 93 0B (ATtiny85)
Error: expected signature for ATmega328P is 1E 95 0F
- double check chip or use -F to carry on regardless
Avrdude done. Thank you.
Failed chip erase: uploading error: exit status 1
This is a stump connected to an UNO for bootloader burn. The AVR did ACK there in the report. How do I use the -f parameter if necessary?
So, you have this kind of boards-- correct?
Connec a board with PC. Goto Device Manager and ceck that the board has appeared as usb device (NOT COM device). Come bcak with the result.
Connect your board directly with the USB-A port of PC.
The system never sees the board. No USB beep. No device manager display.
This is regardless of good bootloader or bad.
Have you connected your board directly with PC? If yes, show the camera picture of the setup.
Are you talking about the Digistump or the UNO r3 ISP?
I plug the stump directly into the laptop usb port.
Pls, show the camera picture.
Amazing. The stump actually runs the onboard code whereas when plugged directly into the port the onboard does not run.
Since I am trying the bootloader process what do you suggest next?
