Successfully ported RTEMS 4.10.2 on MVME5500 VME CPU Board

Kate Feng kate007.feng at gmail.com
Tue May 13 00:55:58 UTC 2014


Joel,

AJAI's  log reveals that he uses mvme5500 BSP.   Porting RTEMS 4.10.2 on
MVME5500
VME CPU Board should be simple and straight forward.  Many users have
demonstrated
their successes via the rtems-users mailing list in the past.

Kate



On Mon, May 12, 2014 at 8:44 AM, Joel Sherrill <Joel.Sherrill at oarcorp.com>wrote:

>  Which BSP did this use? The beaknik or mvme5500?
>
> Did you have any patches?
> On May 12, 2014 6:52 AM, AJAI KUMAR MEDHAVI <akmedhavi at rrcat.gov.in>
> wrote:
> Hi
>
>
> I have successfully ported RTEMS on PowerPC MPC7457 Processor Based VME
> CPU Board MVME5500-0163 with running sample applications.
>
>
> This board has two Flash Memory (Flash0 and Flash1). The MotLoad resides
> on Flash0 (8MB). For Porting I have placed jumper J8 between pins 1 and 2
> to get the board booted from Flash0 (MotLoad).
>
>
> Then I run following commands to download the sample applications.
>
>
> 1. MVME5500>flashShow
>
>    This command shall show in which Flash MotLoad resides.
>
> 2. MVME5500>netShow
>
>    This command shall show which network interface (/dev/enet0 or
> /dev/enet1
>    )is UP. Use UP interface in tftpGet Command.
>
>
> 3. MVME5500>tftpGet -c100.100.100.101  -s100.100.100.110 -g100.100.100.110
> -/d/dev/enet1 -fhello.ralf
>
>
>    Here :
>
>    Client (Target board) IP address : 100.100.100.101
>    Server (Host) IP address : 100.100.100.110
>    Gateway IP Address : 100.100.100.110
>
>
> 2. MVME5500>netShut
>
>
>    Note that the 'netShut' command is important: Modern interface devices
>    usually feature DMA busmasters and    such a busmaster - if not stopped
>    prior to starting RTEMS may corrupt a memory area that was designated as
>    buffer space by MotLoad but has been taken over by the newly started
>    application.
>
>
>
> 3. MVME5500>bmw -af2000000 -bf20fffff -c04000000
>
>
>    Here for Flash0 Memory :
>
>    Destination Starting/Ending Addresses =F2000000/F20FFFFF
>
>    The "-a" and "-b" parameters indicate the start and end addresses of
>    where we want to copy from (the source of the copy.) The "-c" parameter
>    indicates the location to which the data will be copied. In this
> example,
>    we'll copy the data to location 4000000 in main memory.
>
>
>
> 4. MVME5500>rs -nr3 -d0
> 5. MVME5500>rs -nr4 -d0
> 6. MVME5500>go -a0400000
>
>
> Finally following comes on Hyerterminal :
>
>
> Welcome to rtems-4.10.2(PowerPC/Generic (classic FPU)/mvme5500) on
> MVME5500-0163
>
> -----------------------------------------
> Now BSP_mem_size = 0x1FE00000
> Marvell GT64260B (Discovery I) hostbridge detected at bus0 slot0
> BSP unlisted vendor, Bus0 Slot10 DeviceID 0x263388
> TUNDRA PCI-VME bridge detected at bus1 slot0
> Marvell GT64260B (Discovery I) hostbridge detected at bus8 slot0
> BSP unlisted vendor, Bus8 Slot10 DeviceID 0x10088086
> Universe II PCI-VME bridge detected at 0x82000000, IRQ 12
> Universe Master Ports:
> Port  VME-Addr   Size       PCI-Adrs   Mode:
> 0:    0x20000000 0x0E000000 0x90000000 A32, D64 [MBLT], Dat, Sup
> 1:    0x00000000 0x00FF0000 0x9F000000 A24, D64 [MBLT], Dat, Sup
> 2:    0x00000000 0x00010000 0x9FFF0000 A16, D64, Dat, Sup
> 7:    0x00000000 0x01000000 0x9E000000 CSR, D64, Dat, Sup
> Universe Slave Ports:
> Port  VME-Addr   Size       PCI-Adrs   Mode:
> 0:    0x90000000 0x1FE00000 0x00000000 A32, Pgm, Dat, Sup, Usr, PWEN, PREN
> Overriding main IRQ line PCI info with 76
> Registering /dev/console as minor 0 (==/dev/ttyS0)
> WELCOME TO ACCELERATOR CONTROLS .... RTEMS KERNEL ON MVME5500
> enter a string
> bnh
> string read = bnh
>
>
>
>
>
> Best Regards
>
>
> AJAI KUMAR MEDHAVI
> SCIENTIFIC OFFICER
> RAJA RAMMANNA CENTRE FOR ADVANCED TECHNOLGY
> DEPARTMENT OF ATOMIC ENERGY, GOV. OF INDIA,
> PO : CAT, INDORE-452013, INDIA
> PH. 91-731-2488052
>
>
> --
>
>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20140512/c1f84bf7/attachment-0001.html>


More information about the users mailing list