element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Avnet Boards General Lab 9 cpu1 BSP difficulties
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 4 replies
  • Subscribers 367 subscribers
  • Views 570 views
  • Users 0 members are here
Related

Lab 9 cpu1 BSP difficulties

Former Member
Former Member over 9 years ago

Has anyone been doing the SW Speedway series and gotten to the dual processor software development and encountered a problem with creating the second (cpu1) bsp? I get a flood of errors from LONG not being declared.

I had to truncate the error messages to not get labeled as spam.

xemacps_bdring.c:514:13: error: 'LONG' undeclared (first use in this function)
   Status = (LONG)(XST_FAILURE);
             ^
xemacps_bdring.c: At top level:
xemacps_bdring.c:552:1: error: unknown type name 'LONG'
LONG XEmacPs_BdRingToHw(XEmacPs_BdRing * RingPtr, u32 NumBd,
^
xemacps_bdring.c: In function 'XEmacPs_BdRingToHw':
xemacps_bdring.c:557:2: error: unknown type name 'LONG'
  LONG Status;
  ^
xemacps_bdring.c:560:13: error: 'LONG' undeclared (first use in this function)
   Status = (LONG)(XST_SUCCESS);
             ^

(truncated errors)

xemacps.h:780:1: error: unknown type name 'LONG'
LONG XEmacPs_SetTypeIdCheck(XEmacPs *InstancePtr, u32 Id_Check, u8 Index);
^
xemacps.h:782:1: error: unknown type name 'LONG'
LONG XEmacPs_SendPausePacket(XEmacPs *InstancePtr);
^
make[1]: *** [xemacps_sinit.o] Error 1
make[1]: Target `libs' not remade because of errors.
make: *** [ps7_cortexa9_1/libsrc/emacps_v3_1/src/make.libs] Error 2
"Running Make libs in ps7_cortexa9_1/libsrc/gpiops_v3_1/src"
make -C ps7_cortexa9_1/libsrc/gpiops_v3_1/src -s libs  "SHELL=CMD" "COMPILER=arm-xilinx-eabi-gcc" "ARCHIVER=arm-xilinx-eabi-ar" "COMPILER_FLAGS=  -O2 -c" "EXTRA_COMPILER_FLAGS=-g -DUSE_AMP=1"
"Compiling gpiops"
In file included from xgpiops.c:62:0:
xgpiops.h:115:28: fatal error: xplatform_info.h: No such file or directory
#include "xplatform_info.h"
                            ^
compilation terminated.
make[1]: *** [xgpiops.o] Error 1
In file included from xgpiops_g.c:41:0:
xgpiops.h:115:28: fatal error: xplatform_info.h: No such file or directory
#include "xplatform_info.h"
                            ^

compilation terminated.
make[1]: *** [xuartps_sinit.o] Error 1
make[1]: Target `libs' not remade because of errors.
make: *** [ps7_cortexa9_1/libsrc/uartps_v3_1/src/make.libs] Error 2
"Running Make libs in ps7_cortexa9_1/libsrc/usbps_v2_2/src"
make -C ps7_cortexa9_1/libsrc/usbps_v2_2/src -s libs  "SHELL=CMD" "COMPILER=arm-xilinx-eabi-gcc" "ARCHIVER=arm-xilinx-eabi-ar" "COMPILER_FLAGS=  -O2 -c" "EXTRA_COMPILER_FLAGS=-g -DUSE_AMP=1"
"Compiling usbps"
"Running Make libs in ps7_cortexa9_1/libsrc/xadcps_v2_2/src"
make -C ps7_cortexa9_1/libsrc/xadcps_v2_2/src -s libs  "SHELL=CMD" "COMPILER=arm-xilinx-eabi-gcc" "ARCHIVER=arm-xilinx-eabi-ar" "COMPILER_FLAGS=  -O2 -c" "EXTRA_COMPILER_FLAGS=-g -DUSE_AMP=1"
"Compiling xadcps"
make: Target `all' not remade because of errors.

15:26:59 Build Finished (took 11s.438ms)

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    0 Former Member over 9 years ago

    Changes in the Xilinx tools from version to version, especially jumping 4 versions from 2014.4 to 2015.4, can cause issues like this. To run through a step by step tutorial like this one with no issues you will probably need to use the Xilinx tool version, 2014.4, originally targeted. Otherwise you will need to track down the difference. In this case it looks like there has been a change in the ethernet driver code.

     

    If any of our forum users has worked through this issue please respond with the solution.

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Former Member
    0 Former Member over 9 years ago

    Changes in the Xilinx tools from version to version, especially jumping 4 versions from 2014.4 to 2015.4, can cause issues like this. To run through a step by step tutorial like this one with no issues you will probably need to use the Xilinx tool version, 2014.4, originally targeted. Otherwise you will need to track down the difference. In this case it looks like there has been a change in the ethernet driver code.

     

    If any of our forum users has worked through this issue please respond with the solution.

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube