Skip to content

Commit 1428210

Browse files
mheibarsnick
andauthored
Update docs/source/carrierboard_development.rst
Co-authored-by: barsnick <barsnick@users.noreply.github.com>
1 parent cbf50a2 commit 1428210

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/source/carrierboard_development.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ For a random customer, this might look like this (here with a randomly chosen ve
149149
During carrier board manufacturing, it is assumed that writing the EEPROM is done via an external programmer
150150
which is out-of-scope for this documentation.
151151

152-
But during development phase, it might be necessary to exchange the EEPROM content and/or rewrite it for testing purpose.
152+
But during the development phase, it might be necessary to exchange the EEPROM content and/or rewrite it for testing purpose.
153153
Then using an external programmer is cumbersome. Better and simpler is to write the created binary EEPROM image file
154154
into the EEPROM directly from the Charge SOM hooked up to such a carrier board. The following command can be used
155155
via SSH and/or Debug UART:

0 commit comments

Comments
 (0)