Tag: Bootloader

Bootloader ATtiny – Micronucleus

Informatie (ENG): Micronucleus V2.03 ================== Micronucleus is a bootloader designed for AVR ATtiny microcontrollers with a minimal usb interface, cross platform libusb-based program upload tool, and a strong emphasis on bootloader compactness. To the authors knowledge this is, by far, …

Bootloader ATtiny – Micronucleus Read More »

Getagd met ATtiny, ATtiny13, ATtiny25, ATtiny45, ATtiny85, Bootloader, micronucleus, Pinout

Arduino – Bootloader op ATmega chip zetten (USBTinyISP)

Dit voorbeeld laat zien hoe je met een USBTinyISP eenvoudig een bootloader kan zetten op een ATmega chip van een arduino. Hardware Drivers Aansluiten op de Arduino Let op: bovenstaande foto is een voorbeeld, controleer altijd de pinout! Bootloader erop …

Arduino – Bootloader op ATmega chip zetten (USBTinyISP) Read More »

Getagd met ATmega, Bootloader, ISP, USBTinyISP

Hardware Driver – LUFA CDC

Een driver voor LUA CDC Bootloader, te installeren via Apparaatbeheer in Windows: De INF:

;************************************************************
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation
;************************************************************

[DefaultInstall]
CopyINF="LUFA CDC Bootloader.inf"

[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
DriverVer=7/1/2012,10.0.0.0

[Manufacturer]
%MFGNAME%=DeviceList, NTx86, NTamd64, NTia64

[SourceDisksNames]

[SourceDisksFiles]

[DestinationDirs]
DefaultDestDir=12

[DriverInstall]
Include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=DriverInstall.AddReg

[DriverInstall.Services]
Include=mdmcpq.inf
AddService=usbser, 0x00000002, LowerFilter_Service_Inst

[DriverInstall.AddReg]
HKR,,EnumPropPages32,,"msports.dll,SerialPortPropPageProvider"

;------------------------------------------------------------------------------
;  Vendor and Product ID Definitions
;------------------------------------------------------------------------------
; When developing your USB device, the VID and PID used in the PC side
; application program and the firmware on the microcontroller must match.
; Modify the below line to use your VID and PID.  Use the format as shown below.
; Note: One INF file can be used for multiple devices with different VID and PIDs.
; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.
;------------------------------------------------------------------------------
[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTx86]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTamd64]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTia64]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------
;Modify these strings to customize your device
;------------------------------------------------------------------------------
[Strings]
MFGNAME="http://www.lufa-lib.org"
DESCRIPTION="LUFA CDC Class Bootloader"

;************************************************************

; Windows USB CDC ACM Setup File

;************************************************************

[DefaultInstall]

CopyINF="LUFA CDC Bootloader.inf"

[Version]

Signature="$Windows NT$"

Class=Ports

ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}

Provider=%MFGNAME%

DriverVer=7/1/2012,10.0.0.0

[Manufacturer]

%MFGNAME%=DeviceList, NTx86, NTamd64, NTia64

[SourceDisksNames]

[SourceDisksFiles]

[DestinationDirs]

DefaultDestDir=12

[DriverInstall]

Include=mdmcpq.inf

CopyFiles=FakeModemCopyFileSection

AddReg=DriverInstall.AddReg

[DriverInstall.Services]

Include=mdmcpq.inf

AddService=usbser, 0x00000002, LowerFilter_Service_Inst

[DriverInstall.AddReg]

HKR,,EnumPropPages32,,"msports.dll,SerialPortPropPageProvider"

;------------------------------------------------------------------------------

; Vendor and Product ID Definitions

;------------------------------------------------------------------------------

; When developing your USB device, the VID and PID used in the PC side

; application program and the firmware on the microcontroller must match.

; Modify the below line to use your VID and PID. Use the format as shown below.

; Note: One INF file can be used for multiple devices with different VID and PIDs.

; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.

;------------------------------------------------------------------------------

[DeviceList]

%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTx86]

%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTamd64]

%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTia64]

%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

;------------------------------------------------------------------------------

; String Definitions

;------------------------------------------------------------------------------

;Modify these strings to customize your device

;------------------------------------------------------------------------------

[Strings]

MFGNAME="http://www.lufa-lib.org"

DESCRIPTION="LUFA CDC Class Bootloader"

Getagd met 3D printer, Bootloader, CDC, CDCbootloader, Printrboard

Builder 3D Mono – Bricked printrboard verhelpen

Informatie – Bricked printrboard verhelpen Je hebt wel eens van die momenten dat er wat misgaat met uploaden van firmware, resultaat is dan een “bricked” printrboard, geen COM poorten..niets meer… De oplossing is om via de ISP pinnen weer een …

Builder 3D Mono – Bricked printrboard verhelpen Read More »

Getagd met Bootloader, Builder 3D, Builder 3D Solo, Firmware, Flashen, handleidingen, informatie, Printrboard

Hardware Bootloader – Printrboard

Bootloader?: Een bootloader is een computerprogramma dat zorgdraagt voor het starten van het besturingssysteem bij de opstart (bootstrap) van een computer, veel microcontrollers komen zonder bootloader erop gebrand, dat moeten eindgebruikers zelf doen. De Printrboard is uitgerust met een Atmel …

Hardware Bootloader – Printrboard Read More »

Getagd met 3D printer, Arduino ISP, Bootloader, CDC, CDCbootloader, DFU, DFU Bootloader, HID, HID bootloader, informatie, ISP, Main Board, Printrboard

ESP32 – Firmware DEV module Adafruit

Bootlog (Adafruit ESP-WROOM-32 DEV module firmware 2016-06-08)

ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
ets Jun  8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3ffc0000,len:0
load:0x3ffc0000,len:2304
load:0x40078000,len:3788
ho 0 tail 12 room 4
load:0x40098000,len:532
entry 0x4009813c


**************************************
*       hello espressif ESP32!       *
*        2nd boot is running!        *
*            version (V0.1)          *
**************************************
compile time 18:16:58

  SPI Speed      : 40MHz
  SPI Mode       : DIO
  SPI Flash Size : 4MB
Partition Table:
## Label            Usage          Type ST Offset   Length
 0 factory          factory app      00 00 00010000 00100000
 1 rfdata           RF data          01 01 00110000 00040000
 2 wifidata         WiFi data        01 02 00150000 00040000
End of partition table
Loading app partition at offset 00010000
section 0: paddr=0x00000020 vaddr=0x00000000 size=0x0ffe8 ( 65512)
section 1: paddr=0x00010010 vaddr=0x3f400010 size=0x05b64 ( 23396) map
section 2: paddr=0x00015b7c vaddr=0x3ffba720 size=0x01378 (  4984) load
section 3: paddr=0x00016efc vaddr=0x40080000 size=0x00400 (  1024) load
section 4: paddr=0x00017304 vaddr=0x40080400 size=0x126ac ( 75436) load
section 5: paddr=0x000299b8 vaddr=0x00000000 size=0x06658 ( 26200)
section 6: paddr=0x00030018 vaddr=0x400d0018 size=0x325b4 (206260) map
start: 0x400807ac

Initializing heap allocator:
Region 19: 3FFBBA98 len 00024568 tag 0
Region 25: 3FFE8000 len 00018000 tag 1
Pro cpu up.
Pro cpu start user code
nvs_flash_init
frc2_timer_task_hdl:3ffbc564, prio:22, stack:2048
tcpip_task_hdlxxx : 3ffbeca8, prio:20,stack:2048
phy_version: 80, Aug 26 2016, 13:04:06, 0
pp_task_hdl : 3ffc34f0, prio:23, stack:8192

:>enter uart init
uart init wait fifo succeed
exit uart init

IDF version : master(db93bceb)

WIFI LIB version : master(934d079b)

ssc version : master(r283 4d376412)

!!!ready!!!
mode : softAP(26:0a:c4:03:aa:74)
dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)

+WIFI:AP_START

ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0x00

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:2

load:0x3ffc0000,len:0

load:0x3ffc0000,len:2304

load:0x40078000,len:3788

ho 0 tail 12 room 4

load:0x40098000,len:532

entry 0x4009813c

**************************************

* hello espressif ESP32! *

* 2nd boot is running! *

* version (V0.1) *

**************************************

compile time 18:16:58

SPI Speed : 40MHz

SPI Mode : DIO

SPI Flash Size : 4MB

Partition Table:

## Label Usage Type ST Offset Length

0 factory factory app 00 00 00010000 00100000

1 rfdata RF data 01 01 00110000 00040000

2 wifidata WiFi data 01 02 00150000 00040000

End of partition table

Loading app partition at offset 00010000

section 0: paddr=0x00000020 vaddr=0x00000000 size=0x0ffe8 ( 65512)

section 1: paddr=0x00010010 vaddr=0x3f400010 size=0x05b64 ( 23396) map

section 2: paddr=0x00015b7c vaddr=0x3ffba720 size=0x01378 ( 4984) load

section 3: paddr=0x00016efc vaddr=0x40080000 size=0x00400 ( 1024) load

section 4: paddr=0x00017304 vaddr=0x40080400 size=0x126ac ( 75436) load

section 5: paddr=0x000299b8 vaddr=0x00000000 size=0x06658 ( 26200)

section 6: paddr=0x00030018 vaddr=0x400d0018 size=0x325b4 (206260) map

start: 0x400807ac

Initializing heap allocator:

Region 19: 3FFBBA98 len 00024568 tag 0

Region 25: 3FFE8000 len 00018000 tag 1

Pro cpu up.

Pro cpu start user code

nvs_flash_init

frc2_timer_task_hdl:3ffbc564, prio:22, stack:2048

tcpip_task_hdlxxx : 3ffbeca8, prio:20,stack:2048

phy_version: 80, Aug 26 2016, 13:04:06, 0

pp_task_hdl : 3ffc34f0, prio:23, stack:8192

:>enter uart init

uart init wait fifo succeed

exit uart init

IDF version : master(db93bceb)

WIFI LIB version : master(934d079b)

ssc version : master(r283 4d376412)

!!!ready!!!

mode : softAP(26:0a:c4:03:aa:74)

dhcp server start:(ip: 192.168.4.1, mask: 255.255.255.0, gw: 192.168.4.1)

+WIFI:AP_START

Getagd met Adafruit, Boot, Bootloader, ESP-WROOM-32, ESP32, Espressif, Firmware, WROOM

ESP8266 en ESP32- ESPtool (bootloader communicatie)

Website Informatie (ENG) A Python-based, open source, platform independent, utility to communicate with the ROM bootloader in Espressif ESP8266. esptool.py was started by Fredrik Ahlberg (@themadinventor) as an unofficial community project. It is now also supported by Espressif. Current primary …

ESP8266 en ESP32- ESPtool (bootloader communicatie) Read More »

Getagd met Bootloader, chip, Communicatie, ESP8266, ESPtool, Flash

Bootloader – Syslinux

Website Informatie (ENG) The Syslinux Project covers lightweight bootloaders for MS-DOS FAT filesystems (SYSLINUX), network booting (PXELINUX), bootable “El Torito” CD-ROMs (ISOLINUX), and Linux ext2/ext3/ext4 or btrfs filesystems (EXTLINUX). The project also includes MEMDISK, a tool to boot legacy operating …

Bootloader – Syslinux Read More »

Getagd met Bootloader, Syslinux

Firmware via U-Boot bootloader uitlezen

Standaard bied de U-boot bootloader geen mogelijkheid om de data (firmware) op de flash chip op te slaan, wel kan je er naar toe schrijven e.d. Maar je kan wel een HEX dump weer laten geven van de flash chip …

Firmware via U-Boot bootloader uitlezen Read More »

Getagd met Bootloader, Firmware, flash chip, U-boot, Uitlezen

Plugwise Stretch 2.0 – Firmware uploaden (bootloader)

Na wat met de smile te experimenteren en wat testwerk, gaan we nu proberen om ook op de PlugWise Stretch 2.0 nieuwe firmware te plaatsen via een tftp server. Leeswerk: 1) Wat is TFTP. 2) PlugWise Firmware downloaden. 3) UART stick …

Plugwise Stretch 2.0 – Firmware uploaden (bootloader) Read More »

Getagd met Boot environment, Bootloader, Firmware, Plugwise, Stretch 2.0, TFTP, U-boot, UART, uploaden