Chip programming applications like openocd(1) can write new firmware operations to a user configured memory region, supporting advanced features like use of custom bootloaders or EEPROM emulation.
Steps to reproduce
Review openocd(1) documentation
Locate instructions for program
Locate instructions for flash_write
Refer to information about offsets
Expected result
Sendcomm firmware is programmed at the correct memory offset for SAMR34 parts.
Actual result
Programming operations are carried out from the first memory location 0x00000000.
Severity level
This is low priority because project requirements do not mandate user programming.
# Programming offset is unconfigured
## Problem environment
Chip programming applications like *openocd(1)* can write new firmware operations to a user configured memory region, supporting advanced features like use of custom bootloaders or EEPROM emulation.
## Steps to reproduce
1. Review *openocd(1)* documentation
1. Locate instructions for *program*
1. Locate instructions for *flash_write*
1. Refer to information about offsets
## Expected result
Sendcomm firmware is programmed at the correct memory offset for SAMR34 parts.
## Actual result
Programming operations are carried out from the first memory location 0x00000000.
## Severity level
This is **low priority** because project requirements do not mandate user programming.
Programming offset is unconfigured
Problem environment
Chip programming applications like openocd(1) can write new firmware operations to a user configured memory region, supporting advanced features like use of custom bootloaders or EEPROM emulation.
Steps to reproduce
Expected result
Sendcomm firmware is programmed at the correct memory offset for SAMR34 parts.
Actual result
Programming operations are carried out from the first memory location 0x00000000.
Severity level
This is low priority because project requirements do not mandate user programming.