Update docs to reflect bootrom change
This commit is contained in:
@@ -12,7 +12,7 @@ Device Tree Binary (dtb) which details the components of the system.
|
|||||||
The assembly for the BootROM code is located in
|
The assembly for the BootROM code is located in
|
||||||
`generators/testchipip/src/main/resources/testchipip/bootrom/bootrom.S <https://github.com/ucb-bar/testchipip/blob/master/src/main/resources/testchipip/bootrom/bootrom.S>`_.
|
`generators/testchipip/src/main/resources/testchipip/bootrom/bootrom.S <https://github.com/ucb-bar/testchipip/blob/master/src/main/resources/testchipip/bootrom/bootrom.S>`_.
|
||||||
The BootROM address space starts at ``0x10000`` (determined by the ``BootROMParams`` key in the configuration) and execution starts at address
|
The BootROM address space starts at ``0x10000`` (determined by the ``BootROMParams`` key in the configuration) and execution starts at address
|
||||||
``0x10040`` (given by the linker script and reset vector in the ``BootROMParams``), which is marked by the ``_hang`` label in the BootROM assembly.
|
``0x10000`` (given by the linker script and reset vector in the ``BootROMParams``), which is marked by the ``_hang`` label in the BootROM assembly.
|
||||||
|
|
||||||
The Chisel generator encodes the assembled instructions into the BootROM
|
The Chisel generator encodes the assembled instructions into the BootROM
|
||||||
hardware at elaboration time, so if you want to change the BootROM code, you
|
hardware at elaboration time, so if you want to change the BootROM code, you
|
||||||
|
|||||||
@@ -34,7 +34,7 @@ Probe an address on the target system:
|
|||||||
|
|
||||||
.. code-block:: shell
|
.. code-block:: shell
|
||||||
|
|
||||||
./uart_tsi +tty=/dev/ttyUSBX +init_read=0x10040 none
|
./uart_tsi +tty=/dev/ttyUSBX +init_read=0x10000 none
|
||||||
|
|
||||||
Write some address before running a program:
|
Write some address before running a program:
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user