<div dir="ltr">Is there now a list of wiki pages that need to be deleted?<div><br></div><div>Thank you and I'm glad to see this patch. :)</div><div><br></div><div>--joel</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 2, 2020 at 4:54 PM Chris Johns <<a href="mailto:chrisj@rtems.org">chrisj@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Pushed and again thank you for doing this.<br>
<br>
Chris<br>
<br>
On 2020-04-02 19:49, Mritunjay wrote:<br>
> Fixed trailing spaces.<br>
> ---<br>
> user/bsps/bsps-m68k.rst | 190 +++++++++++++++++++++++++++++++++++++++-<br>
> 1 file changed, 188 insertions(+), 2 deletions(-)<br>
> <br>
> diff --git a/user/bsps/bsps-m68k.rst b/user/bsps/bsps-m68k.rst<br>
> index 60882fb..bdb516b 100644<br>
> --- a/user/bsps/bsps-m68k.rst<br>
> +++ b/user/bsps/bsps-m68k.rst<br>
> @@ -53,7 +53,19 @@ TODO.<br>
> mcf5329<br>
> =======<br>
> <br>
> -TODO.<br>
> +Overview<br>
> +--------<br>
> +<br>
> +This BSP is heavily based on the MCF5235 BSP. The MCF5329EVB is a Motorola<br>
> +evaluation board (Zoom) with a LogicPD MCF5329-10 SODIMM-144 card. The<br>
> +development kit features the MCF5329 based Fire Engine, as well as a plug-in<br>
> +system-on-module containing 32 MB of DDR-SDRAM. The board also includes 2 MB of<br>
> +boot flash, 16 MB of NAND flash, a core frequency of 240MHz, an onboard 800x600<br>
> +LCD controller, FEC, USB, uarts, CAN bus, QSPI, I2C, and 10/100 Ethernet.<br>
> +<br>
> +You can find the link to MCF5329 Reference Manual below:<br>
> +<br>
> +* `MCF5329 Reference Manual <<a href="https://www.nxp.com/docs/en/reference-manual/MCF5329RM.pdf" rel="noreferrer" target="_blank">https://www.nxp.com/docs/en/reference-manual/MCF5329RM.pdf</a>>`_<br>
> <br>
> mrm332<br>
> ======<br>
> @@ -73,7 +85,181 @@ TODO.<br>
> mvme162<br>
> =======<br>
> <br>
> -TODO.<br>
> +Overview<br>
> +--------<br>
> +<br>
> +The MVME162 family provides OEMs and solution developers an ideal platform for<br>
> +embedded monitoring and control apllications it allows an OEM to minimize<br>
> +engineering expenses while integrating value-added hardware and software<br>
> +applications onto an off-the-shelf product. In order to provide the wide range<br>
> +of solutions, the MVME162 allows a variety of MPU, memory, and interface<br>
> +options such as floating-point, Ethernet, SCSI, and VME. The result is a<br>
> +variation of the MVME162 which most closely fits the application requirement.<br>
> +<br>
> +There are a large number of model variations on this board. This was the first<br>
> +user submitted BSP and continues to be a fairly popular simply because at one<br>
> +point it was the highest selling VMEBus board of all time.<br>
> +<br>
> +Board Setup<br>
> +-----------<br>
> +<br>
> +We will setup the RTEMS Lab Board initally to proceed further for the setup<br>
> +of TFTP transfer.<br>
> +<br>
> +The env settings are:<br>
> +<br>
> +.. code-block:: none<br>
> +<br>
> + MPU Clock Speed =25Mhz<br>
> + 162-Bug>env<br>
> + Bug or System environment [B/S] = B?<br>
> + Field Service Menu Enable [Y/N] = N?<br>
> + Remote Start Method Switch [G/M/B/N] = B?<br>
> + Probe System for Supported I/O Controllers [Y/N] = Y?<br>
> + Negate VMEbus SYSFAIL* Always [Y/N] = N?<br>
> + Local SCSI Bus Reset on Debugger Startup [Y/N] = N?<br>
> + Local SCSI Bus Negotiations Type [A/S/N] = A?<br>
> + Industry Pack Reset on Debugger Startup [Y/N] = Y?<br>
> + Ignore CFGA Block on a Hard Disk Boot [Y/N] = Y?<br>
> + Auto Boot Enable [Y/N] = N?<br>
> + Auto Boot at power-up only [Y/N] = Y?<br>
> + Auto Boot Controller LUN = 00?<br>
> + Auto Boot Device LUN = 00?<br>
> + Auto Boot Abort Delay = 15?<br>
> + Auto Boot Default String [NULL for a empty string] = ?<br>
> + ROM Boot Enable [Y/N] = N?<br>
> + ROM Boot at power-up only [Y/N] = Y?<br>
> + ROM Boot Enable search of VMEbus [Y/N] = N?<br>
> + ROM Boot Abort Delay = 0?<br>
> + ROM Boot Direct Starting Address = FF800000?<br>
> + ROM Boot Direct Ending Address = FFDFFFFC?<br>
> + Network Auto Boot Enable [Y/N] = N?<br>
> + Network Auto Boot at power-up only [Y/N] = Y?<br>
> + Network Auto Boot Controller LUN = 00?<br>
> + Network Auto Boot Device LUN = 00?<br>
> + Network Auto Boot Abort Delay = 5?<br>
> + Network Auto Boot Configuration Parameters Pointer (NVRAM) = FFE0FF00?<br>
> + Memory Search Starting Address = 00000000?<br>
> + Memory Search Ending Address = 01000000?<br>
> + Memory Search Increment Size = 00010000?<br>
> + Memory Search Delay Enable [Y/N] = N?<br>
> + Memory Search Delay Address = FFFFD20F?<br>
> + Memory Size Enable [Y/N] = Y?<br>
> + Memory Size Starting Address = 00000000?<br>
> + Memory Size Ending Address = 01000000?<br>
> + Base Address of Dynamic Memory = 00000000?<br>
> + Size of Parity Memory = 00000000?<br>
> + Size of ECC Memory Board #0 = 01000000?<br>
> + Size of ECC Memory Board #1 = 00000000?<br>
> + Base Address of Static Memory = FFE00000?<br>
> + Size of Static Memory = 00020000?<br>
> + Slave Enable #1 [Y/N] = Y?<br>
> + Slave Starting Address #1 = 00000000?<br>
> + Slave Ending Address #1 = 00FFFFFF?<br>
> + Slave Address Translation Address #1 = 00000000?<br>
> + Slave Address Translation Select #1 = 00000000?<br>
> + Slave Control #1 = 03FF?<br>
> + Slave Enable #2 [Y/N] = N?<br>
> + Slave Starting Address #2 = 00000000?<br>
> + Slave Ending Address #2 = 00000000?<br>
> + Slave Address Translation Address #2 = 00000000?<br>
> + Slave Address Translation Select #2 = 00000000?<br>
> + Slave Control #2 = 0000?<br>
> + Master Enable #1 [Y/N] = Y?<br>
> + Master Starting Address #1 = 01000000?<br>
> + Master Ending Address #1 = EFFFFFFF?<br>
> + Master Control #1 = 0D?<br>
> + Master Enable #2 [Y/N] = N?<br>
> + Master Starting Address #2 = 00000000?<br>
> + Master Ending Address #2 = 00000000?<br>
> + Master Control #2 = 00?<br>
> + Master Enable #3 [Y/N] = N?<br>
> + Master Starting Address #3 = 00000000?<br>
> + Master Ending Address #3 = 00000000?<br>
> + Master Control #3 = 00?<br>
> + Master Enable #4 [Y/N] = N?<br>
> + Master Starting Address #4 = 00000000?<br>
> + Master Ending Address #4 = 00000000?<br>
> + Master Address Translation Address #4 = 00000000?<br>
> + Master Address Translation Select #4 = 00000000?<br>
> + Master Control #4 = 00?<br>
> + Short I/O (VMEbus A16) Enable [Y/N] = Y?<br>
> + Short I/O (VMEbus A16) Control = 01?<br>
> + F-Page (VMEbus A24) Enable [Y/N] = Y?<br>
> + F-Page (VMEbus A24) Control = 02?<br>
> + ROM Access Time Code = 03?<br>
> + FLASH Access Time Code = 02?<br>
> + MCC Vector Base = 05?<br>
> + VMEC2 Vector Base #1 = 06?<br>
> + VMEC2 Vector Base #2 = 07?<br>
> + VMEC2 GCSR Group Base Address = D2?<br>
> + VMEC2 GCSR Board Base Address = 00?<br>
> + VMEbus Global Time Out Code = 01?<br>
> + Local Bus Time Out Code = 02?<br>
> + VMEbus Access Time Out Code = 02?<br>
> + IP A Base Address = 00000000?<br>
> + IP B Base Address = 00000000?<br>
> + IP C Base Address = 00000000?<br>
> + IP D Base Address = 00000000?<br>
> + IP D/C/B/A Memory Size = 00000000?<br>
> + IP D/C/B/A General Control = 00000000?<br>
> + IP D/C/B/A Interrupt 0 Control = 00000000?<br>
> + IP D/C/B/A Interrupt 1 Control = 00000000?<br>
> +<br>
> +To setup the Server/Client IP Addresses for the TFTP Transfer, we will use the<br>
> +NIOT command. NIOT (Network I/O Teach) is a 162-Bug's debugger command commonly<br>
> +used to setup the Server/Client IP Addresses for the TFTP Transfer.<br>
> +<br>
> +The NIOT command goes something like this:<br>
> +<br>
> +.. code-block:: none<br>
> +<br>
> + 162-Bug>niot<br>
> + Controller LUN =00?<br>
> + Device LUN =00?<br>
> + Node Control Memory Address =FFE10000?<br>
> + Client IP Address =192.168.1.245?<br>
> + Server IP Address =192.168.1.92?<br>
> + Subnet IP Address Mask =255.255.255.0?<br>
> + Broadcast IP Address =192.168.1.255?<br>
> + Gateway IP Address =0.0.0.0?<br>
> + Boot File Name ("NULL" for None) =/mvme162.img?<br>
> + Argument File Name ("NULL" for None) =?<br>
> + Boot File Load Address =00020000?<br>
> + Boot File Execution Address =00020000?<br>
> + Boot File Execution Delay =00000000?<br>
> + Boot File Length =00000000?<br>
> + Boot File Byte Offset =00000000?<br>
> + BOOTP/RARP Request Retry =00?<br>
> + TFTP/ARP Request Retry =00?<br>
> + Trace Character Buffer Address =00000000?<br>
> + BOOTP/RARP Request Control: Always/When-Needed (A/W)=A?<br>
> + BOOTP/RARP Reply Update Control: Yes/No (Y/N) =Y?<br>
> +<br>
> +Downloading and Executing<br>
> +--------------------------<br>
> +Download from the TFTP server using the 162-Bug's "NBO"<br>
> +(Network Boot Operating System) command:<br>
> +<br>
> +.. code-block:: none<br>
> +<br>
> + 162-Bug>nbo<br>
> + Network Booting from: VME162, Controller 0, Device 0<br>
> + Loading: /mvme162.img<br>
> +<br>
> + Client IP Address = 192.168.1.245<br>
> + Server IP Address = 192.168.1.92<br>
> + Gateway IP Address = 0.0.0.0<br>
> + Subnet IP Address Mask = 255.255.255.0<br>
> + Boot File Name = /mvme162.img<br>
> + Argument File Name =<br>
> +<br>
> + Network Boot File load in progress... To abort hit <BREAK><br>
> +<br>
> + Bytes Received =&356528, Bytes Loaded =&356528<br>
> + Bytes/Second =&89132, Elapsed Time =4 Second(s)<br>
> +<br>
> +The program will automatically run when download is complete.<br>
> <br>
> mvme167<br>
> =======<br>
> <br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div>