EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: unknown type name 'DBLINK'
From: Heinz Junkes via Core-talk <core-talk at aps.anl.gov>
To: Michael Davidsaver <mdavidsaver at gmail.com>
Cc: core-talk at aps.anl.gov
Date: Sat, 12 Mar 2022 21:32:45 +0100 
;-)

MVME6100> tftpGet -a04000000 -c141.14.139.12 -s141.14.131.192 -m255.255.240.0 -g141.14.128.128 -flibComTestHarness.boot
Network Loading from: /dev/enet0
Loading File: libComTestHarness.boot
Load Address: 04000000
Download Buffer Size = User Defined

Client IP Address      = 141.14.139.12
Server IP Address      = 141.14.131.192
Gateway IP Address     = 141.14.128.128
Subnet IP Address Mask = 255.255.240.0

Network File Load in Progress...

Bytes Received =&6617180, Bytes Loaded =&6617180
Bytes/Second   =&3308590, Elapsed Time =2 Second(s)
MVME6100> waitProbe
System I/O Probe Complete
MVME6100> netShut
/dev/-----------------------------------------
config addr is 0xf1000cf8
config data is 0xf1000cfc
Welcome to RTEMS rtems-6.0.0 (PowerPC/Generic (classic FPU)/beatnik)
CPU: MPC7457
Board Type: MVME6100-0163 (S/N D00967A)
Bus Clock Freq:   133333333 Hz
CPU Clock Freq:  1266666654 Hz
Memory:           536870912 bytes
-----------------------------------------
Now BSP_mem_size = 0x1fe00000
Configuration.work_space_size = 2033c50
Page table setup finished; will activate it NOW...
Going to start PCI buses scanning and initialization
Number of PCI buses found is : 3
MSR 0x2003032
Exit from bspstart
unable to find the universe in pci config space
Tundra Tsi148 PCI-VME bridge detected at 0x81100000, IRQ 84
Tsi148 Outbound Ports:
Port  VME-Addr   Size       PCI-Adrs   Mode:
0:    0x20000000 0x0e000000 0x90000000 A32, SUP, D32, SCT
1:    0x00000000 0x00ff0000 0x9f000000 A24, SUP, D32, SCT
2:    0x00000000 0x00010000 0x9fff0000 A16, SUP, D32, SCT
7:    0x00000000 0x01000000 0x9e000000 CSR, SUP, D32, SCT
Tsi148 Inbound Ports:
Port  VME-Addr   Size       PCI-Adrs   Mode:
0:    0x90000000 0x1fe00000 0x00000000 A32, PGM, DAT, SUP, USR, MBLT, BLT
vmeTsi148 IRQ manager: looking for registers on VME...
Trying to find CSR on VME...
vmeTsi148 - IRQ manager using VME CSR to flush FIFO
Registering /dev/console as minor 0 (==/dev/ttyS0)
WARNING: OS Clock time was read before being set.
Using 1990-01-
0 2i n0i0t:C0o0n:s0o0l.e0 0-0-0-0 0I nUfToC
---
stdin: fileno: 0, ttyname: /dev/console
stdout: fileno: 1, ttyname: /dev/console
stderr: fileno: 2, ttyname: /dev/console
time set to : 04/14/14 07:30:06.000001229 UTC
Startup.
epicsThreadSetPriority called by non epics thread

***** RTEMS Version: rtems-6.0.0 (PowerPC/Generic (classic FPU)/beatnik) *****

***** Initializing network (libbsd, dhcpcd) *****
nexus0: <RTEMS Nexus device>
mve0 on nexus0
miibus0: <MII bus> on mve0
ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus0
ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
info: mve0: Ethernet address: ec:9e:cd:23:c8:41

***** ifconfig lo0 *****
info: lo0: link state changed to UP

***** add dhcpcd hook *****

***** Start default network dhcpcd *****

--Info (hpj)-- bsd task prio IRQS: 96  -----
i
--Info (hpj)-- bsd task prio TIME: 98  -----
n
 ---- Waiting for DHCP ...
fo: version 6.2.1 starting
info: mve0: link state changed to DOWN
debug: mve0: executing `ioc boot' PREINIT

dhcpcd ---> 'interface=mve0'
  'interface' = 'mve0'
dhcpcd ---> 'reason=PREINIT'
  'reason' = 'PREINIT'
dhcpcd ---> 'pid=1'
dhcpcd ---> 'ifmetric=201'
dhcpcd ---> 'ifwireless=0’

...


   EPICS Test Harness Results
    ==========================

All tests successful.
Programs=38, Tests=3128, 355 wallclock secs



> On 12. Mar 2022, at 20:45, Michael Davidsaver <mdavidsaver at gmail.com> wrote:
> 
> On 3/12/22 11:24, Heinz Junkes wrote:
>> Bull's eye
>> I could have thought of it myself ;-(
>> more ./rtems/6/powerpc-rtems6/beatnik/lib/include/link.h
> 
> Ok.  So the first '-I'
> 
>> .../powerpc-rtems6-gcc  -fasm  -I/home/rtems/MVME6100_WORK/rtems/6/powerpc-rtems6/beatnik/lib/include ...
> 
> needs to be shifted to the end, or included with '-isystem /...'.
> 
> https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html
Replies:
Re: unknown type name 'DBLINK' Andrew Johnson via Core-talk
References:
unknown type name 'DBLINK' Heinz Junkes via Core-talk
Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk
Re: unknown type name 'DBLINK' Heinz Junkes via Core-talk
Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk
Navigate by Date:
Prev: Re: unknown type name 'DBLINK' Heinz Junkes via Core-talk
Next: Re: unknown type name 'DBLINK' Andrew Johnson via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 
Navigate by Thread:
Prev: Re: unknown type name 'DBLINK' Heinz Junkes via Core-talk
Next: Re: unknown type name 'DBLINK' Andrew Johnson via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024