KONNEKTING Wiki - User contributions [en]

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-02-18T21:05:12Z

E.burkowski: /* Porting beta4 to beta5 */

== New and Noteworthy ==

New things and features in beta5 are:

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart'''

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

File:SolderKNXpins1.jpg

2019-10-08T15:23:08Z

E.burkowski: E.burkowski uploaded a new version of File:SolderKNXpins1.jpg

== Licensing ==
{{GPL}}

Solder contact pins for KNX terminal

2019-10-08T15:14:10Z

E.burkowski: Created page with "= What do we need = * KNX terminal without cable * 2x pins * PCB * solder iron (about 25 W is enough) * soldering tin File:SolderKNXpins1.jpg = Steps = == Step 1 == Plac..."

= What do we need =
* KNX terminal without cable
* 2x pins
* PCB
* solder iron (about 25 W is enough)
* soldering tin
[[File:SolderKNXpins1.jpg]]

= Steps =
== Step 1 ==
Place the KNX terminal upside down on table and put pins in it

[[File:SolderKNXpins2.jpg]]

== Step 2 ==
Put PCB on KNX terminal. Pins should go through the holes.
PCB may stay tilted, but it is no problem.
[[File:SolderKNXpins3.jpg]]

== Step 3 ==
Turn the PCB in the direction, so you can easily access one of KNX pins.
Put soldering tin on a contact area and heat it up with a solder iron. Put enough solder tin on it. Whole pin and contact area should be covered.
[[File:SolderKNXpins4.jpg]]

== Step 4 ==
Please check if KNX terminal is tilted or not. If yes, hold the PCB parallel to a table with KNX terminal upside down and heat up contact area. Now you can place terminal in a good position. After it let it cool down.
[[File:SolderKNXpins5.jpg]]

== Step 5 ==
Now, you can solder the second contact.

[[File:SolderKNXpins6.jpg]]

File:SolderKNXpins6.jpg

2019-10-08T15:08:17Z

E.burkowski:

== Licensing ==
{{GPL}}

File:SolderKNXpins5.jpg

2019-10-08T15:08:01Z

E.burkowski:

== Licensing ==
{{GPL}}

File:SolderKNXpins4.jpg

2019-10-08T15:06:15Z

E.burkowski:

== Licensing ==
{{GPL}}

File:SolderKNXpins3.jpg

2019-10-08T15:05:50Z

E.burkowski:

== Licensing ==
{{GPL}}

File:SolderKNXpins2.jpg

2019-10-08T14:56:08Z

E.burkowski:

== Licensing ==
{{GPL}}

File:SolderKNXpins1.jpg

2019-10-08T14:55:47Z

E.burkowski:

== Licensing ==
{{GPL}}

Documentation

2019-10-08T14:49:14Z

E.burkowski:

== Software ==

* [[KONNEKTING Suite]]
* [[KONNEKTING Device Library]]

== Specifications ==

* [[KONNEKTING Device Specification]]
* [[KONNEKTING XML Device Description]]
* [[KONNEKTING Modular DIN RAIL Device Specification]]
* [[KONNEKTING Protocol Specification]]

== Technical Documentation ==

* [[Recommended Arduino Boards]]
* [[Programming Workflow]]
* [[FOTB - Firmware Over The Bus]]
* [[SAMD Flash Overview]]

== HowTos ==

* [[Solder contact pins for KNX terminal]]

== Research ==

* [[Tiny-BCU]]

Recommended Arduino Boards

2019-01-07T19:25:52Z

E.burkowski: /* Boards we can recommend */

= Clarification =

We focus on devices found on www.arduino.cc and support following chips for following devices:

* Atmel ATmega 328P
** Arduino Nano
** Arduino ProMini
* Atmel ATmega 32U4
** Arduino Leonardo
** Arduino Micro
* Atmel/Microchip SAMD21G18
** Arduino Zero

Our [[KONNEKTING Device Library]] has been developed and tested against the following platforms:

* Arduino.cc default ATmega based boards
* Arduino.cc SAMD Boards: https://github.com/arduino/ArduinoCore-samd

It is totally okay to use cheap Arduino boards from ebay or aliexpress, but you should be aware of the matching type of board according to the board-definitions of the platforms we use.

Our current and clear recommendation is, to use a SAM21G18 based board, as the chip provides 32k RAM and 256k Memory and 48Mhz clock speed. So plenty of space and performance at lowest possible current consumption.

Be aware that there are different SAMD boards out there:

* Boards which refer to "M0"
* Boards which refer to "Zero"

Both use different bootloader and both use in general differen pin-definitions. So you cannot really use the same sketch on both. You have to adapt to the few differences they have.

= Boards we can recommend =
== WeMos SAMD21 mini ==
https://img.staticbg.com/thumb/large/oaupload/banggood/images/87/BD/4f4ad980-0b6a-4b20-bf06-bf7c12d9b2e6.JPG

This board uses Arduino Zero Bootloader. It has '''no''' OnBoard (pin 13) LED.

P.S. This board was neither developed nor produced by WeMos... So you can't find it on WeMos homepage...

== WeMos SAMD21 ==
https://img.staticbg.com/thumb/large/oaupload/banggood/images/A0/49/8528801a-ee06-424a-8d87-57d4f9ba22a1.jpg

This board is "big brother" of '''WeMos SAMD21 mini'''.
It has a standard Arduino UNO R3 pin layout with additional RX(31) and TX(30) pins (UART name: Serial)

== Elecrow Crowduino M0 SD ==

https://www.elecrow.com/media/catalog/product/cache/1/small_image/9df78eab33525d08d6e5fb8d27136e95/1/4/14649511760.jpg

https://www.elecrow.com/crowduino-m0-sd-p-1649.html

'''Attention:''' this boards runs a "M0 bootloader". Please ensure that you select the correct board in Arduino IDE. It's "Arduino M0 Pro (Native USB Port)". [[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) to be verified ...

== Adafruit ItsyBitsy M0 Express ==

https://www.exp-tech.de/media/image/a0/ff/74/adafruit_itsybits_m0_express_circuit_python_02.jpg

https://www.exp-tech.de/plattformen/arduino/8448/adafruit-itsybitsy-m0-express-circuitpython-arduino-ide
'''
Board-Selection:''' to-be-done

Project status

2018-08-23T18:08:26Z

E.burkowski: /* Version */

== Version ==

=== 1.0.0 beta 1 ===
'''Released!'''

=== 1.0.0 beta 2 ===
'''Released!'''

=== 1.0.0 beta 3 ===
'''Released!'''

=== 1.0.0 beta 4 ===
'''Released!'''

=== 1.0.0 beta 4a ===
'''Released!'''

Changelog:

* Preparation for beta5
* refactorings
* added some more helper stuf like header-files for DPT
* smaller bugfixes

Migration from beta4:

const int KonnektingDevice::_numberOfParams = sizeof (_paramSizeList);

''_numberOfParams'' is no longer of type byte, it's now integer, as preparation for beta5. But beta4a is still only supportig max. 256 params.

byte(*eepromReadFunc)(int);
void (*eepromWriteFunc)(int, byte);
void (*eepromUpdateFunc)(int, byte);
void (*eepromCommitFunc)(void);

The value attributes are no longer ''int'', but ''byte'', as our storage is only capable of handling one byte per storagecell/index.

=== 1.0.0 beta 4b ===
'''Released!''' See Arduino Library Manager for download.

Changelog:
* new telegram reception behavior: stay in task() until reception is complete
* fix for infinity init-read requests
* new DPTs: 7.600, 242.600, 251.600
* updated demo sketches: easier board setting handling

=== 1.0.0 beta 5 ===
''' in progress '''

=== 1.0.0 stable ===
''' planned '''

== Roadmap ==

-> [[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) Stand 2018/02/19 '''work in progress'''

* '''Spezifikation allgemeine Hardware-Anforderungen 100%'''
* '''Beta-Version der Software … 100%'''
** '''… um die HW anzutreiben … 100%'''
** '''… um die HW zu programmieren/parametrisieren … 100%'''
* '''Spezifikation Geräterichtlinien … 100%'''
** '''Spezifikation REG-Gerät … 100%'''
*** '''Standard-Gehäuse … 100%'''
*** '''Komponentenanordnung … 100%'''
*** '''Platinenaufbau … 100%'''
*** '''Verbindungsstecker … 100%'''
** Spezifikation UP-Gerät
*** Siemens BCU basiert
*** KNX Transceiver basiert
** Spezifikation AP-Gerät
** '''Erstes serienreifes REG-Gerät … 100%'''
*** '''Erster serienreife Controllerplatine … 100%'''
*** '''Erste serienreife Reg-Applikationsplatine … 100%'''
*** '''Erste serienreife Reg-Frontendplatine … 100%'''
* Software von „Beta“ auf „Stable“ bringen.
* KONNEKTING Developer Tool, mit dem man die .kdevice.xml konfortabel zusammenklicken kann
* Plattform/Anlaufstelle für den „Vertrieb“ schaffen.
* Ziel: Ein interessierter Nutzer kann sich aus einer Auswahl von Bausätzen das passende KNX Gerät aussuchen, „bestellen“ und es in Eigenregie ohne Spezialkenntnisse oder Spezialwissen fertig aufbauen.

SAMD Flash Overview

2018-03-20T22:22:57Z

E.burkowski:

Applicable for SAMD21x18 with 256k FLASH

'''EFU - External Flash Update'''
{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x3FFF (16k)
|2nd stage update bootloader, last 256 bytes (0x05F00-0x05FFF) Bootloader EEPROM
|-
|0x06000-0x3DFFF
|0x38000 (224k)
|Sketch
|-
|0x3E000-0x3FFFF
|0x2000 (8k)
|8k virtual "flash EEPROM"
|}

'''IFU - Internal Flash Update'''
{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x3FFF (16k)
|2nd stage update bootloader, last 256 bytes (0x05F00-0x05FFF) Bootloader EEPROM
|-
|0x06000-0x21FFF
|0x1C000 (112k)
|Sketch
|-
|0x22000-0x3DFFF
|0x1C000 (112k)
|Update
|-
|0x3E000-0x3FFFF
|0x2000 (8k)
|8k virtual "flash EEPROM"
|}

Some additional information:
*SAMD21G18A has 256 KByte FLASH
*PAGE size is 64 Byte
*One ROW has 4 pages.
*Before one PAGE can be written, whole ROW that contains this PAGE must be erased.

=> the minimum writeble amount of data is 256 bytes (1 ROW/4 PAGES).

'''Example''': you will write some bytes to page 1. Pages 0,2 and 3 are on the same ROW.
Pages 0,2 and 3 contains already some date.
#So you have to read the data of this 3 pages to an array
#add data of page 1 to this array
#erase whole row (=pages 0,1,2,3)
#and then write whole row(=pages 0,1,2,3)

SAMD Flash Overview

2018-03-18T17:26:05Z

E.burkowski:

Applicable for SAMD21x18 with 256k FLASH

'''EFU - External Flash Update'''
{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x3FFF (16k)
|2nd stage update bootloader, last 256 bytes (0x05F00-0x05FFF) Bootloader EEPROM
|-
|0x06000-0x3DFFF
|0x38000 (224k)
|Sketch
|-
|0x3E000-0x3FFFF
|0x2000 (8k)
|8k virtual "flash EEPROM"
|}

'''IFU - Internal Flash Update'''
{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x3FFF (16k)
|2nd stage update bootloader, last 256 bytes (0x05F00-0x05FFF) Bootloader EEPROM
|-
|0x06000-0x21FFF
|0x1C000 (112k)
|Sketch
|-
|0x22000-0x3DFFF
|0x1C000 (112k)
|Update
|-
|0x3E000-0x3FFFF
|0x2000 (8k)
|8k virtual "flash EEPROM"
|}

Some additional information:
SAMD21G18A has 256 KByte FLASH
Page size is 64 Byte
Row has 4 pages.
Before a page can be written, the row that contains the page must be erased.

=> the minimum writeble amount of data is 256 bytes (1 Row/4 Pages)

MicroBCU

2018-03-16T23:41:23Z

E.burkowski:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU
|-
! colspan="2"|[[File:MicroBCU_top.png|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU_bottom.png|300px|thumb|center]]
|-
! Developer
| Eugen Burkowski
|-
! Status
| released
|-
! Microcontroller/Board
| universal
|}

== Description ==
A little Bus Coupler Unit with an UART interface

== Hardware ==
*IC: NCN5120
*Size: 23 x 19 x 5.4 (10.3) mm
*Voltage 1: 3.3V
*Voltage 2 (optinal): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1

== User Documentation ==
the new version (R1.2) has to connectors:
* 7x pin 2.54mm THT
* 2x4 or 2x5 pin 1.27 SMD
[[File:MicroBCU_pins.png|378px]]

Attention: MicroBCU has no dedicated pins for WAGO terminal (Red/Grey)!

== Developer Documentation ==

== Build It ==

== Links ==
[https://github.com/KONNEKTING/KonnektingHardware/tree/master/MicroBCU]
[https://knx-user-forum.de/forum/projektforen/konnekting/1045398-microbcu-sehr-kleiner-knx-transceiver]

[[Category:Device/Kits]]

File:MicroBCU bottom.png

2018-03-16T23:38:15Z

E.burkowski:

File:MicroBCU top.png

2018-03-16T23:37:48Z

E.burkowski:

MicroBCU

2018-03-16T23:25:30Z

E.burkowski: /* Links */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Foo Bar Device Kit
|-
! colspan="2"|[[File:foobar.jpg|300px|thumb|center]]
|-
! Developer
| foo bar
|-
! Status
| foo bar
|-
! Microcontroller/Board
| foo bar
|-
! KNX connectivity
| foo bar
|-
! Needed libraries
| bar foo<br />foo bar
|}

== Description ==
A little Bus Coupler Unit with an UART interface

== Hardware ==
*IC: NCN5120
*Size: 23 x 19 x 5.4 (10.3) mm
*Voltage 1: 3.3V
*Voltage 2 (optinal): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1

== User Documentation ==
the new version (R1.2) has to connectors:
* 7x pin 2.54mm THT
* 2x4 or 2x5 pin 1.27 SMD
[[File:MicroBCU_pins.png|378px]]

Attention: MicroBCU has no dedicated pins for WAGO terminal (Red/Grey)!

== Developer Documentation ==

== Build It ==

== Links ==
[https://github.com/KONNEKTING/KonnektingHardware/tree/master/MicroBCU]
[https://knx-user-forum.de/forum/projektforen/konnekting/1045398-microbcu-sehr-kleiner-knx-transceiver]

[[Category:Device/Kits]]

MicroBCU

2018-03-16T23:22:25Z

E.burkowski: /* Hardware */

MicroBCU

2018-03-16T23:21:38Z

E.burkowski: /* User Documentation */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Foo Bar Device Kit
|-
! colspan="2"|[[File:foobar.jpg|300px|thumb|center]]
|-
! Developer
| foo bar
|-
! Status
| foo bar
|-
! Microcontroller/Board
| foo bar
|-
! KNX connectivity
| foo bar
|-
! Needed libraries
| bar foo<br />foo bar
|}

== Description ==
A little Bus Coupler Unit with an UART interface

== Hardware ==
*IC: NCN5120
*Size: 23 x 19 x 5.4 (10.3) mm
*Voltage 1: 3.3V
*Voltage 2 (optinal): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA

== User Documentation ==
the new version (R1.2) has to connectors:
* 7x pin 2.54mm THT
* 2x4 or 2x5 pin 1.27 SMD
[[File:MicroBCU_pins.png|378px]]

Attention: MicroBCU has no dedicated pins for WAGO terminal (Red/Grey)!

== Developer Documentation ==

== Build It ==

== Links ==
[https://github.com/KONNEKTING/KonnektingHardware/tree/master/MicroBCU]

[[Category:Device/Kits]]

File:MicroBCU pins.png

2018-03-16T23:21:00Z

E.burkowski:

MicroBCU

2018-03-16T23:19:18Z

E.burkowski: /* User Documentation */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Foo Bar Device Kit
|-
! colspan="2"|[[File:foobar.jpg|300px|thumb|center]]
|-
! Developer
| foo bar
|-
! Status
| foo bar
|-
! Microcontroller/Board
| foo bar
|-
! KNX connectivity
| foo bar
|-
! Needed libraries
| bar foo<br />foo bar
|}

== Description ==
A little Bus Coupler Unit with an UART interface

== Hardware ==
*IC: NCN5120
*Size: 23 x 19 x 5.4 (10.3) mm
*Voltage 1: 3.3V
*Voltage 2 (optinal): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA

== User Documentation ==
the new version (R1.2) has to connectors:
* 7x pin 2.54mm THT
* 2x4 or 2x5 pin 1.27 SMD
[[File:MicroBCU_pins.jpg]378px]

Attention: MicroBCU has no dedicated pins for WAGO terminal (Red/Grey)!

== Developer Documentation ==

== Build It ==

== Links ==
[https://github.com/KONNEKTING/KonnektingHardware/tree/master/MicroBCU]

[[Category:Device/Kits]]

MicroBCU

2018-03-16T23:13:33Z

E.burkowski: Created page with "{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;" ! colspan="2"|Foo Bar Device Kit |- ! colspan="2"|File:foobar.jpg|300px|thu..."

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Foo Bar Device Kit
|-
! colspan="2"|[[File:foobar.jpg|300px|thumb|center]]
|-
! Developer
| foo bar
|-
! Status
| foo bar
|-
! Microcontroller/Board
| foo bar
|-
! KNX connectivity
| foo bar
|-
! Needed libraries
| bar foo<br />foo bar
|}

== Description ==
A little Bus Coupler Unit with an UART interface

== Hardware ==
*IC: NCN5120
*Size: 23 x 19 x 5.4 (10.3) mm
*Voltage 1: 3.3V
*Voltage 2 (optinal): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA

== User Documentation ==
the new version (R1.2) has to connectors:
* 7x pin 2.54mm THT
* 2x4 or 2x5 pin 1.27 SMD

== Developer Documentation ==

== Build It ==

== Links ==
[https://github.com/KONNEKTING/KonnektingHardware/tree/master/MicroBCU]

[[Category:Device/Kits]]

FOTB - Firmware Over The Bus

2018-03-12T13:52:53Z

E.burkowski:

See: https://github.com/arduino/ArduinoCore-samd/pull/220

Steps:

Get SDUBoot.ino from https://github.com/arduino/ArduinoCore-samd/tree/master/libraries/SDU/extras/SDUBoot. Use this as starting point for an own version, let's say we name our version "EFUBoot"

So we will have

EFUBoot\
EFUBoot\EFUBoot.ino

and we also need

EFUBoot\boot
EFUBoot\build.sh

build.sh should contain something like this:

<syntaxhighlight lang=bash line>
#!/bin/sh -x

ARDUINO=$ARDUINO_HOME/arduino
SKETCH_NAME="EFUBoot.ino"
SKETCH="$PWD/$SKETCH_NAME"
BUILD_PATH="$PWD/build"
OUTPUT_PATH="./boot"

if [[ "$OSTYPE" == "darwin"* ]]; then
ARDUINO="/Applications/Arduino.app/Contents/MacOS/Arduino"
fi

buildSDUBootSketch() {
BOARD=$1
DESTINATION=$2

$ARDUINO --verify --board $BOARD --preserve-temp-files --pref build.path="$BUILD_PATH" $SKETCH
cat "$BUILD_PATH/$SKETCH_NAME.bin" | xxd -i > $DESTINATION
rm -rf "$BUILD_PATH"
}

mkdir -p "$OUTPUT_PATH"

buildSDUBootSketch "arduino:samd:arduino_zero_edbg" "$OUTPUT_PATH/zero.h"
</syntaxhighlight>

Make it executable with help of

chmod g+x build.sh

And finally run it with

./build.sh

After that, you have a .h file in your boot-folder.

Copy/paste SDU.cpp/SDU.h and let them point to the .h file you just created.

Write your sketch and include your version of SDU.h/SDU.cpp with "#include".
Upload your sketch as usual.

If you now apply you update according to your own SDUBoot variant and reboot your arduino, the new sketch is applied to main memory and arduino starts up with the new sketch.

Some additional information:
https://github.com/arduino/ArduinoCore-samd/issues/247

Normaly the ardunio Bootloader is placed on 0x0000 address on internal flash and a user sketch starts on 0x2000.

With the so called "2nd stage bootloader" you have:
# the normal arduino bootloader on 0x0000, which is resposible for USB-Sketch updates
# 2nd stage bootloader placed on 0x2000 instead of user sketch
# user sketch placed on 0x6000

linker script, that builds firmware file for arduino update, has two sections:

<syntaxhighlight>KEEP(*(.sketch_boot))
. = ALIGN(0x2000);
KEEP(*(.isr_vector))
*(.text*)</syntaxhighlight>

.sketch_boot will be used only with/for 2nd stage bootloader. this section is defined in sdu.cpp:
<syntaxhighlight>__attribute__ ((section(".sketch_boot")))
unsigned char sduBoot[0x4000] = {
#if defined(ARDUINO_SAMD_ZERO)
#include "boot/zero.h" </syntaxhighlight>
zero.h is compiled SDUBoot.ino sketch => .bin file converted to a .h file.
array of size 0x4000 will be placed on 0x2000. So the user sketch starts at 0x6000

.isr_vector is user sketch. if 2nd stage doesn't exist, user sketch will be placed on 0x2000, other way it will be placed right after 2nd stage bootloader (0x2000 + 0x4000(size of 2nd stage bootloader) => 0x6000).

= KONNEKTING FOTB Workflow =

to be done

FOTB - Firmware Over The Bus

2018-03-12T09:44:56Z

E.burkowski:

See: https://github.com/arduino/ArduinoCore-samd/pull/220

Steps:

Get SDUBoot.ino from https://github.com/arduino/ArduinoCore-samd/tree/master/libraries/SDU/extras/SDUBoot. Use this as starting point for an own version, let's say we name our version "EFUBoot"

So we will have

EFUBoot\
EFUBoot\EFUBoot.ino

and we also need

EFUBoot\boot
EFUBoot\build.sh

build.sh should contain something like this:

<syntaxhighlight lang=bash line>
#!/bin/sh -x

ARDUINO=$ARDUINO_HOME/arduino
SKETCH_NAME="EFUBoot.ino"
SKETCH="$PWD/$SKETCH_NAME"
BUILD_PATH="$PWD/build"
OUTPUT_PATH="./boot"

if [[ "$OSTYPE" == "darwin"* ]]; then
ARDUINO="/Applications/Arduino.app/Contents/MacOS/Arduino"
fi

buildSDUBootSketch() {
BOARD=$1
DESTINATION=$2

$ARDUINO --verify --board $BOARD --preserve-temp-files --pref build.path="$BUILD_PATH" $SKETCH
cat "$BUILD_PATH/$SKETCH_NAME.bin" | xxd -i > $DESTINATION
rm -rf "$BUILD_PATH"
}

mkdir -p "$OUTPUT_PATH"

buildSDUBootSketch "arduino:samd:arduino_zero_edbg" "$OUTPUT_PATH/zero.h"
</syntaxhighlight>

Make it executable with help of

chmod g+x build.sh

And finally run it with

./build.sh

After that, you have a .h file in your boot-folder.

Copy/paste SDU.cpp/SDU.h and let them point to the .h file you just created.

Write your sketch and include your version of SDU.h/SDU.cpp with "#include".
Upload your sketch as usual.

If you now apply you update according to your own SDUBoot variant and reboot your arduino, the new sketch is applied to main memory and arduino starts up with the new sketch.

Some additional information:
https://github.com/arduino/ArduinoCore-samd/issues/247

Normaly the ardunio Bootloader is placed on 0x0000 address on internal flash and a user sketch starts on 0x2000.

With the so called "2nd stage bootloader" you have:
# the normal arduino bootloader on 0x0000, which is resposible for USB-Sketch updates
# 2nd stage bootloader placed on 0x2000 instead of user sketch
# user sketch placed on 0x6000

linker script, that builds firmware file for arduino update, has two sections:

<syntaxhighlight>KEEP(*(.sketch_boot))
. = ALIGN(0x2000);
KEEP(*(.isr_vector))
*(.text*)</syntaxhighlight>

# .sketch_boot will be used only with/for 2nd stage bootloader.
# .isr_vector is user sketch. if 2nd stage doesn't exist, user sketch will be placed on 0x2000, other way it will be placed right after 2nd stage bootloader (0x2000 + 0x4000(size of 2nd stage bootloader) => 0x6000).

SAMD Flash Overview

2018-03-12T08:11:46Z

E.burkowski:

Applicable for SAMD21x18 with 256k FLASH

'''EFU - External Flash Update'''
{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x3FFF (16k)
|2nd stage update bootloader, last 256 bytes (0x05EFF-0x05FFF) Bootloader EEPROM
|-
|0x06000-0x3DFFF
|0x38000 (224k)
|Sketch
|-
|0x3E000-0x3FFFF
|0x2000 (8k)
|8k virtual "flash EEPROM"
|}

'''IFU - Internal Flash Update'''
{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x3FFF (16k)
|2nd stage update bootloader, last 256 bytes (0x05EFF-0x05FFF) Bootloader EEPROM
|-
|0x06000-0x21FFF
|0x1C000 (112k)
|Sketch
|-
|0x22000-0x3DFFF
|0x1C000 (112k)
|Update
|-
|0x3E000-0x3FFFF
|0x2000 (8k)
|8k virtual "flash EEPROM"
|}

Some additional information:
SAMD21G18A has 256 KByte FLASH
Page size is 64 Byte
Row has 4 pages.
Before a page can be written, the row that contains the page must be erased.

=> the minimum writeble amount of data is 256 bytes (1 Row/4 Pages)

SAMD Flash Overview

2018-03-09T15:21:07Z

E.burkowski:

SAMD Flash Overview

2018-03-08T10:15:46Z

E.burkowski:

SAMD Flash Overview

2018-03-08T10:14:31Z

E.burkowski:

SAMD Flash Overview

2018-03-08T10:08:51Z

E.burkowski:

{| class="wikitable"
!style="text-align:center"|address
!style="text-align:center"|size
!style="text-align:center"|Description
|-
|0x00000-0x01FFF
|0x2000 (8k)
|Arduino Bootloader
|-
|0x02000-0x05FFF
|0x4000 (16k)
|2nd stage update bootloader
|-
|0x06000-0x21FFF
|0x1C000 (112k)
|Sketch
|-
|0x22000-0x3DFFF
|0x1C000 (112k)
|Update
|-
|0x3E000-0x3FFFF
|0x2000(8k)
|8k virtual "flash EEPROM"
|}

FOTB - Firmware Over The Bus

2018-03-08T08:48:27Z

E.burkowski: