You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/documents/board/emsdp.rst
+34-25Lines changed: 34 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,68 +112,77 @@ Before the interfaces are used, you must install the required drivers on the com
112
112
the MetaWare debugger or other serial debug consoles (such as PuTTY or other hyper-terminals).
113
113
114
114
The driver is a part of the Digilent Adept tool. You can download the most recent version of
115
-
the Digilent Adept tool from the Digilent website at https://store.digilentinc.com, and follow the installation instructions provided by Digilent.
115
+
the Digilent Adept tool from the `Digilent website <https://store.digilentinc.com>`_, and follow the installation instructions provided by Digilent.
116
116
117
117
You may also skip this step if you are using default settings.
118
118
119
119
.. note:: Learn more about programming FPGA device in `ARC_EM_SDP_UserGuide`
120
120
121
121
Package Preparation
122
122
^^^^^^^^^^^^^^^^^^^
123
-
This section talks about how to add new |emsdp| cores into embARC OSP.
124
-
If you are using default cores of |emsdp|: *em6_scss*, *em7d_esp_dfss*, and *em11d_dfss*, then you may skip this section.
123
+
This section talks about how to add new |emsdp| cores into embARC OSP. Please notice that the existing em11d_dfss core configure files are for test and example purpose, we strongly suggest you to follow the steps in this section.
125
124
126
-
#. You may download the package from our website. Suppose you want to add a new package called ``em9d_dfss``, your package name would be ``emsdp_em9d_dfss.zip``.
125
+
#. You may download the package from our website: `DesignWare ARC EM Software Development Platform <https://www.synopsys.com/dw/ipdir.php?ds=arc-em-software-development-platform>`_. Suppose you want to add a new package called ``em11d_dfss``, then the name of your downloaded package would be ``emsdp_em11d_dfss.zip``.
127
126
128
-
#. Download the package and unzip it, you will find four folders: ``/doc``, ``/fpga``, ``/include``, ``/tool_config``. Now create a new folder according to your board revision and package name. In this case *em9d_dfss* is added to *rev2* board, so you should set your directory as this:``/board/emsdp/rev2/configs/em9d_dfss``
127
+
#. Unzip the .zip file, you will find four folders: ``/doc``, ``/fpga``, ``/include``, ``/tool_config``. Now create a new folder according to your board revision and package name. In this case *em11d_dfss* is added to *rev2* board, so you should set your directory as this:``/board/emsdp/rev2/configs/em11d_dfss``
129
128
130
-
#. Copy the content of unzipped folder to ``/board/emsdp/rev2/configs/em9d_dfss``. It would be like:
129
+
#. Copy the contents of unzipped folder to ``/board/emsdp/rev2/configs/em11d_dfss``. It would be like:
131
130
132
-
.. code-block:: console
131
+
.. code-block:: console
133
132
134
-
em9d_dfss
135
-
├─doc
136
-
├─fpga
137
-
├─include
138
-
└─tool_config
133
+
em11d_dfss
134
+
├─doc
135
+
├─fpga
136
+
├─include
137
+
└─tool_config
139
138
140
139
141
-
#. You are done importing a new package, flash the bit file into board and build with it to make sure everything is working.
140
+
#. You are done importing a new package, flash the bit file into your board and then build with it to make sure everything is working.
142
141
143
-
Run Your First Program
144
-
^^^^^^^^^^^^^^^^^^^^^^
145
-
By setting up the board, you are now ready to run your first program on |emsdp|.
146
-
please refer to example `example_blinky` for further details. Build and download the example using either MetaWare or GNU. The command is shown below:
142
+
Build and Run Your First Program
143
+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
144
+
By setting up the board, you are now ready to run your first program on |emsdp|. There are two way to run your program.
145
+
The first way is to use debugger, please refer to example `example_blinky` for further details. Build and download the example using either MetaWare or GNU. The command is shown below:
147
146
148
-
.. code-block:: console
147
+
.. code-block:: console
149
148
150
-
$ cd <embarc_root>/example/baremetal/blinky
151
-
$ gmake BOARD=emsdp BD_VER=rev2 CORE=em11d_dfss TOOLCHAIN=mw run
149
+
$ cd <embarc_root>/example/baremetal/blinky
150
+
$ gmake BOARD=emsdp BD_VER=rev2 CORE=em11d_dfss TOOLCHAIN=mw run
152
151
153
152
.. note:: Notice that for CORE option there are multiple core choices, please check `<embarc_root>/board/emsdp/rev2` folder for available cores.
154
153
154
+
The second way is to use a micro-SD card, the bootloader on |emsdp| is capable to find and run prebuilt bin file that is named as ``app.bin``.
155
+
Build the example using either MetaWare or GNU with the command shown below:
156
+
157
+
.. code-block:: console
158
+
159
+
$ cd <embarc_root>/example/baremetal/blinky
160
+
$ gmake BOARD=emsdp BD_VER=rev2 CORE=em11d_dfss TOOLCHAIN=mw bin
161
+
162
+
After building succeed, you will find ``blinky_mw_em11d_dfss.bin`` at ``<embarc_root>/example/baremetal/blinky/obj_emsdp_rev2/mw_em11d_dfss``. Rename the bin file to ``app.bin`` and copy to the root directory of a micro-SD card. Insert the micro-SD card to |emsdp| board and press start button to run.
163
+
155
164
Development Guide
156
165
^^^^^^^^^^^^^^^^^
157
166
Please refer to `Developer Guides`.
158
167
You may need to specify peripheral driver (`<embarc_root>/device/peripheral`) for your own code.
159
168
160
169
For example, if Wi-Fi rs9113 driver is needed, add this line in makefile:
161
170
162
-
.. code-block:: console
171
+
.. code-block:: console
163
172
164
-
EXT_DEV_LIST += wifi/rs9113
173
+
EXT_DEV_LIST += wifi/rs9113
165
174
166
175
Another example is to add both wifi driver and audio codec driver for an online audio application:
167
176
168
-
.. code-block:: console
177
+
.. code-block:: console
169
178
170
-
EXT_DEV_LIST += wifi/rs9113 audio/max9880a
179
+
EXT_DEV_LIST += wifi/rs9113 audio/max9880a
171
180
172
181
173
182
Contributing
174
183
^^^^^^^^^^^^
175
184
|emsdp| is welcome to your contribution. If you found any bug or issue or have suggestions,
176
-
please feel free to raise issues or pull requests at [embARC Open Software Platform](https://github.com/foss-for-synopsys-dwc-arc-processors/embarc_osp) repository on GitHub.
185
+
please feel free to raise issues or pull requests at `embARC Open Software Platform<https://github.com/foss-for-synopsys-dwc-arc-processors/embarc_osp>`_ repository on GitHub.
Copy file name to clipboardExpand all lines: doc/documents/getting_started/peripheral_preparation.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Other PMOD or Compatible Modules
74
74
`Pmod AD2 <https://reference.digilentinc.com/reference/pmod/pmodad2/start>`_ : ADC type is AD7991, use **I2C** for data collection.
75
75
Driver code at ``embarc_osp/device/peripheral/adc/ad7991``.
76
76
77
-
`ESP01\/ESP01S <http://wiki.ai-thinker.com/esp8266/docs>`_ : Primary IC type is ESP8266, use **UART** interface for data changing and controlling.
77
+
`ESP01\/ESP01S <https://wiki.ai-thinker.com/esp8266/docs>`_ : Primary IC type is ESP8266, use **UART** interface for data changing and controlling.
78
78
Driver code at ``embarc_osp/device/peripheral/wifi/slip_esp``.
79
79
80
-
The ESP01/ESP01S module is not originally a PMOD module, however it is PMOD compatible, meaning that you could wire it to PMOD interface on board. You need to connect GND(embARC) to GND(ESP) , 3.3V(embARC) to VCC(ESP), RXD(embARC) to TXD(ESP), and TXD(embARC) to RXD(ESP), respectively. Please take reference from datasheet of `ESP01\/ESP01S <http://wiki.ai-thinker.com/esp8266/docs>`_ and UART (type 4A) part of `Digilent Pmod Spec <https://www.digilentinc.com/Pmods/Digilent-Pmod_%20Interface_Specification.pdf>`_ for pin layout.
80
+
The ESP01/ESP01S module is not originally a PMOD module, however it is PMOD compatible, meaning that you could wire it to PMOD interface on board. You need to connect GND(embARC) to GND(ESP) , 3.3V(embARC) to VCC(ESP), RXD(embARC) to TXD(ESP), and TXD(embARC) to RXD(ESP), respectively. Please take reference from datasheet of `ESP01\/ESP01S <https://wiki.ai-thinker.com/esp8266/docs>`_ and UART (type 4A) part of `Digilent Pmod Spec <https://www.digilentinc.com/Pmods/Digilent-Pmod_%20Interface_Specification.pdf>`_ for pin layout.
0 commit comments