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
  • 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 Some problem on QEMU of Petalinux
  • 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 Not Answered
  • Replies 4 replies
  • Subscribers 358 subscribers
  • Views 2030 views
  • Users 0 members are here
Related

Some problem on QEMU of Petalinux

chenzhenyuch
chenzhenyuch over 8 years ago

Hi
Linux is booting up ok

I have test my app on QEMU simulation system.

I have got the warning belows when running the CMD:  "petalinux-boot --qemu --kernel".

 

INFO: The image provided is a zImage
WARNING: The QEMU subnet settings is 192.168.10.1/255.255.255.0. It is different from the one configured in PetaLinux /
WARNING: To enable the network of the QEMU MicroBlaze system. Please change the Network settings of PetaLinux and rebuild it or manually configure the network when the QEMU MicroBlaze system is boot
WARNING: Do you want to contine? (y/n)

 

  y
  INFO: TCP PORT is free 
  INFO: Starting arm QEMU
  INFO:  qemu-system-aarch64 -L /opt/pkg/petalinux/petalinux-v2015.4-final/etc/qemu -M arm-generic-fdt-plnx -machine linux=on  -net nic,vlan=1 -net tap,vlan=1,script=/opt/pkg/petalinux/petalinux-v2015.4-final/tools/common/petalinux/utils/petalinux-qemu-ifup -net nic,vlan=2 -net tap,vlan=2,script=/opt/pkg/petalinux/petalinux-v2015.4-final/tools/common/petalinux/utils/petalinux-qemu-ifup -net nic,vlan=3 -net tap,vlan=3,script=/opt/pkg/petalinux/petalinux-v2015.4-final/tools/common/petalinux/utils/petalinux-qemu-ifup -net nic,vlan=4 -net tap,vlan=4,script=/opt/pkg/petalinux/petalinux-v2015.4-final/tools/common/petalinux/utils/petalinux-qemu-ifup  -serial /dev/null -serial mon:stdio -display none -kernel /home/z/user/qemu/Avnet-Digilent-ZedBoard-2015.4/build/qemu_image.elf -gdb tcp::9000 -dtb system.dtb  -device loader,addr=0xf8000008,data=0xDF0D,data-len=4 -device loader,addr=0xf8000140,data=0x00500801,data-len=4 -device loader,addr=0xf800012c,data=0x1ed044d,data-len=4 -device loader,addr=0xf8000108,data=0x0001e008,data-len=4  
  --------------------------------------------------------------------
  Xilinx QEMU Dec 10 2015 13:38:20.
  --------------------------------------------------------------------
  INFO: Configuring tap0 for QEMU
  INFO: Configuring tap1 for QEMU
  INFO: Configuring tap2 for QEMU
  INFO: Configuring tap3 for QEMU
  Warning: hub port hub4port0 has no peer
  Warning: vlan 4 with no nics
  Warning: hub port hub3port0 has no peer
  Warning: vlan 3 with no nics
  Warning: netdev hub3port0 has no peer
  Warning: netdev hub4port0 has no peer
  Warning: requested NIC (anonymous, model unspecified) was not created (not supported by this machine?)
  Warning: requested NIC (anonymous, model unspecified) was not created (not supported by this machine?)
  Uncompressing Linux... done, booting the kernel.
  Booting Linux on physical CPU 0x0
  Linux version 4.0.0-xilinx (root@ubuntu) (gcc version 4.9.2 (Sourcery CodeBench Lite 2015.05-17) ) #3 SMP PREEMPT Thu Aug 10 00:17:50 PDT 2017
  CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
  CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
  Machine model: Avnet-Digilent-ZedBoard-2015.4
  bootconsole [earlycon0] enabled
  cma: Reserved 16 MiB at 0x1f000000
  Memory policy: Data cache writealloc
  PERCPU: Embedded 11 pages/cpu @debce000 s12672 r8192 d24192 u45056
  Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
  Kernel command line: console=ttyPS0,115200 earlyprintk
  PID hash table entries: 2048 (order: 1, 8192 bytes)
  Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
  Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
  Memory: 492872K/524288K available (4759K kernel code, 223K rwdata, 1708K rodata, 3364K init, 208K bss, 15032K reserved, 16384K cma-reserved, 0K highmem)
  Virtual kernel memory layout:
      vector  : 0xffff0000 - 0xffff1000   (   4 kB)
      fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
      vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
      lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
      pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
      modules : 0xbf000000 - 0xbfe00000   (  14 MB)
        .text : 0xc0008000 - 0xc0658efc   (6468 kB)
        .init : 0xc0659000 - 0xc09a2000   (3364 kB)
        .data : 0xc09a2000 - 0xc09d9de0   ( 224 kB)
         .bss : 0xc09d9de0 - 0xc0a0e0f4   ( 209 kB)
  Preemptible hierarchical RCU implementation.
  Additional per-CPU info printed with stalls.
  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
  RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
  NR_IRQS:16 nr_irqs:16 16
  L2C: platform modifies aux control register: 0x00000000 -> 0x30400000
  L2C: DT/platform modifies aux control register: 0x00000000 -> 0x30400000
  L2C-310 errata 588369 769419 enabled
  L2C-310 full line of zeros enabled for Cortex-A9
  L2C-310 cache controller enabled, 8 ways, 64 kB
  L2C-310: CACHE_ID 0x00000000, AUX_CTRL 0x00000000
  slcr mapped to e0804000
  zynq_clock_init: clkc starts at e0804100
  Zynq clock init
  sched_clock: 64 bits at 216MHz, resolution 4ns, wraps every 2537334505472ns
  timer #0 at e0808000, irq=17
  Console: colour dummy device 80x30
  Calibrating delay loop... 1506.50 BogoMIPS (lpj=7532544)
  pid_max: default: 32768 minimum: 301
  Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
  Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
  CPU: Testing write buffer coherency: ok
  CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
  Setting up static identity map for 0x481788 - 0x4817e0
  CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
  Brought up 2 CPUs
  SMP: Total of 2 processors activated (3133.44 BogoMIPS).
  CPU: WARNING: CPU(s) started in wrong/inconsistent modes (primary CPU mode 0x13)
  CPU: This may indicate a broken bootloader or firmware.
  devtmpfs: initialized
  VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0
  pinctrl core: initialized pinctrl subsystem
  NET: Registered protocol family 16
  DMA: preallocated 256 KiB pool for atomic coherent allocations
  cpuidle: using governor ladder
  cpuidle: using governor menu
  zynq_get_revision: no devcfg node found
  hw-breakpoint: debug architecture 0x4 unsupported.
  vgaarb: loaded
  SCSI subsystem initialized
  usbcore: registered new interface driver usbfs
  usbcore: registered new interface driver hub
  usbcore: registered new device driver usb
  media: Linux media interface: v0.10
  Linux video capture interface: v2.00
  pps_core: LinuxPPS API ver. 1 registered
  pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
  PTP clock support registered
  EDAC MC: Ver: 3.0.0
  Advanced Linux Sound Architecture Driver Initialized.
  Switched to clocksource arm_global_timer
  NET: Registered protocol family 2
  TCP established hash table entries: 4096 (order: 2, 16384 bytes)
  TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
  TCP: Hash tables configured (established 4096 bind 4096)
  TCP: reno registered
  UDP hash table entries: 256 (order: 1, 8192 bytes)
  UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
  NET: Registered protocol family 1
  RPC: Registered named UNIX socket transport module.
  RPC: Registered udp transport module.
  RPC: Registered tcp transport module.
  RPC: Registered tcp NFSv4.1 backchannel transport module.
  futex hash table entries: 512 (order: 3, 32768 bytes)
  jffs2: version 2.2. (NAND) (SUMMARY)  Copyright 2001-2006 Red Hat, Inc.
  io scheduler noop registered
  io scheduler deadline registered
  io scheduler cfq registered (default)
  zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
  dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
  dma-pl330 f8003000.dmac: DBUFF-256x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
  e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 25, base_baud = 992063) is a xuartps
  console [ttyPS0] enabled
  console [ttyPS0] enabled
  bootconsole [earlycon0] disabled
  bootconsole [earlycon0] disabled
  [drm] Initialized drm 1.1.0 20060810
  brd: module loaded
  loop: module loaded
  m25p80 spi0.0: s25fl256s1 (32768 Kbytes)
  4 ofpart partitions found on MTD device spi0.0
  Creating 4 MTD partitions on "spi0.0":
  0x000000000000-0x000000500000 : "boot"
  0x000000500000-0x000000520000 : "bootenv"
  0x000000520000-0x000000fa0000 : "kernel"
  0x000000fa0000-0x000002000000 : "spare"
  CAN device driver interface
  libphy: MACB_mii_bus: probed
  mdio_bus e000b000.etherne: /amba/ethernet@e000b000/mdio has invalid PHY address
  mdio_bus e000b000.etherne: scan phy mdio at address 0
  mdio_bus e000b000.etherne: scan phy mdio at address 1
  mdio_bus e000b000.etherne: scan phy mdio at address 2
  mdio_bus e000b000.etherne: scan phy mdio at address 3
  mdio_bus e000b000.etherne: scan phy mdio at address 4
  mdio_bus e000b000.etherne: scan phy mdio at address 5
  mdio_bus e000b000.etherne: scan phy mdio at address 6
  mdio_bus e000b000.etherne: scan phy mdio at address 7
  mdio_bus e000b000.etherne: scan phy mdio at address 8
  mdio_bus e000b000.etherne: scan phy mdio at address 9
  mdio_bus e000b000.etherne: scan phy mdio at address 10
  mdio_bus e000b000.etherne: scan phy mdio at address 11
  mdio_bus e000b000.etherne: scan phy mdio at address 12
  mdio_bus e000b000.etherne: scan phy mdio at address 13
  mdio_bus e000b000.etherne: scan phy mdio at address 14
  mdio_bus e000b000.etherne: scan phy mdio at address 15
  mdio_bus e000b000.etherne: scan phy mdio at address 16
  mdio_bus e000b000.etherne: scan phy mdio at address 17
  mdio_bus e000b000.etherne: scan phy mdio at address 18
  mdio_bus e000b000.etherne: scan phy mdio at address 19
  mdio_bus e000b000.etherne: scan phy mdio at address 20
  mdio_bus e000b000.etherne: scan phy mdio at address 21
  mdio_bus e000b000.etherne: scan phy mdio at address 22
  mdio_bus e000b000.etherne: scan phy mdio at address 23
  mdio_bus e000b000.etherne: scan phy mdio at address 24
  mdio_bus e000b000.etherne: scan phy mdio at address 25
  mdio_bus e000b000.etherne: scan phy mdio at address 26
  mdio_bus e000b000.etherne: scan phy mdio at address 27
  mdio_bus e000b000.etherne: scan phy mdio at address 28
  mdio_bus e000b000.etherne: scan phy mdio at address 29
  mdio_bus e000b000.etherne: scan phy mdio at address 30
  mdio_bus e000b000.etherne: scan phy mdio at address 31
  macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 27 (00:0a:35:00:1e:53)
  macb e000b000.ethernet eth0: attached PHY driver [Marvell 88E1111] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
  e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
  e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
  ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
  ehci-pci: EHCI PCI platform driver
  usbcore: registered new interface driver usb-storage
  e0002000.usb supply vbus not found, using dummy regulator
  ULPI transceiver vendor/product ID 0x0424/0x0004
  ULPI integrity check: passed.
  ci_hdrc ci_hdrc.0: doesn't support gadget
  ci_hdrc ci_hdrc.0: EHCI Host Controller
  ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
  ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
  hub 1-0:1.0: USB hub found
  hub 1-0:1.0: 6 ports detected
  mousedev: PS/2 mouse device common for all mice
  i2c /dev entries driver
  Xilinx Zynq CpuIdle Driver started
  Driver 'mmcblk' needs updating - please use bus_type methods
  sdhci: Secure Digital Host Controller Interface driver
  sdhci: Copyright(c) Pierre Ossman
  sdhci-pltfm: SDHCI platform and OF driver helper
  ledtrig-cpu: registered to indicate activity on CPUs
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver
  TCP: cubic registered
  NET: Registered protocol family 17
  can: controller area network core (rev 20120528 abi 9)
  NET: Registered protocol family 29
  can: raw protocol (rev 20120528)
  can: broadcast manager protocol (rev 20120528 t)
  can: netlink gateway (rev 20130117) max_hops=1
  zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
  zynq_pm_late_init: Unable to map DDRC IO memory.
  zynq_pm_remap_ocm: no compatible node found for 'xlnx,zynq-ocmc-1.0'
  zynq_pm_suspend_init: Unable to map OCM.
  Registering SWP/SWPB emulation handler
  /opt/pkg/petalinux/petalinux-v2015.4-final/components/linux-kernel/xlnx-4.0/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
  ALSA device list:
    No soundcards found.
  Freeing unused kernel memory: 3364K (c0659000 - c09a2000)
  INIT: version 2.88 booting
  Creating /dev/flash/* device nodes
  random: dd urandom read with 0 bits of entropy available
  Starting internet superserver: inetd.
  update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
   Removing any system startup links for run-postinsts ...
    /etc/rcS.d/S99run-postinsts
  INIT: Entering runlevel: 5
  Configuring network interfaces... udhcpc (v1.23.1) started
  Sending discover...
  macb e000b000.ethernet eth0: link up (1000/Full)
  Sending discover...
  Sending discover...
  No lease, forking to background
  done.
   
  Built with PetaLinux v2015.4 (Yocto 1.8) Avnet-Digilent-ZedBoard-2015_4 /dev/ttyPS0
   

Another problem is that eth0  have no response and forking to background.  

I have highlighted these two logs. Could you please help to resolve it. 

Thanks very much.

  • Sign in to reply
  • Cancel
  • jafoste4
    0 jafoste4 over 8 years ago

    Hello,

    What training are you going through?

    --Josh

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • chenzhenyuch
    0 chenzhenyuch over 8 years ago in reply to jafoste4

    Hello JFoster,

    I have used the  QEMU system Emulator to run the GDB. However it failed to launch the QEMU.

    I have copied the cmd and error logs as follows:

    1. petalinux-create -t project -s

    /opt/pkg/Avnet-Digilent-ZedBoard-v2015.4-final.bsp
     
    2. petalinux-create -t apps --name myapp --template c
     
    3.petalinux-config -c rootfs
     
    I have selected: apps->myapp & Debugging->build debugable applications. Then save the process.
     
    4.  petalinux-build.  Successfully build the image and kernel.
     
    5,Please see the logs:
      Built with PetaLinux v2015.4 (Yocto 1.8) Avnet-Digilent-ZedBoard-2015_4 /dev/ttyPS0
      Avnet-Digilent-ZedBoard-2015_4 login: root
      Password: 
      login[856]: root login on 'ttyPS0'
      root@Avnet-Digilent-ZedBoard-2015_4:~# ls /bin | grep myapp
      myapp
      root@Avnet-Digilent-ZedBoard-2015_4:~# myapp
      Hello, PetaLinux World!
      cmdline args:
      myapp
       
      I can run it on the QEMU successfully.
       
      However, it fails to run when I run the GDB.
       
      7. I have run the cmd:
      root@Avnet-Digilent-ZedBoard-2015_4:~#  gdbserver host:1534 /bin/myapp
      Process /bin/myapp created; pid = 907
      Listening on port 1534
       
      8.Then  I have opened another command console and type the following cmd:
       
     
       root@ubuntu:/home/z/user/qemu/Avnet-Digilent-ZedBoard-2015.4/build/linux/rootfs/apps# ls
     
       echo_test  fwupgrade  mat_mul_demo  myapp  peekpoke  proxy_app
     
       root@ubuntu:/home/z/user/qemu/Avnet-Digilent-ZedBoard-2015.4/build/linux/rootfs/apps# petalinux-util --gdb myapp
     
       GNU gdb (Sourcery CodeBench Lite 2015.05-17) 7.7.50.20140217-cvs
     
       Copyright (C) 2014 Free Software Foundation, Inc.
     
       License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
     
       This is free software: you are free to change and redistribute it.
     
       There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
     
       and "show warranty" for details.
     
       This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-xilinx-linux-gnueabi".
     
       Type "show configuration" for configuration details.
     
       For bug reporting instructions, please see:
     
       <https://sourcery.mentor.com/GNUToolchain/>.
     
       Find the GDB manual and other documentation resources online at:
     
       <http://www.gnu.org/software/gdb/documentation/>.
     
       For help, type "help".
     
       Type "apropos word" to search for commands related to "word"...
     
       myapp: No such file or directory.
     
        
     
        
     
       9 Attach to the QEMU target in GDB by running the following GDB command:
     
       (gdb) target remote :9000
     
      
        Remote debugging using :9000
      
        0xc001cba8 in ?? ()
      
        (gdb) continue
      
        Continuing.
      
         
     
       
    It seems that gdb have no response.
     
     
    Could you please help to resolve my problem
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • chenzhenyuch
    0 chenzhenyuch over 8 years ago

    I have tried the CMD referring to the UG982. I have got the following logs, It doesn't work also.

    root@ubuntu:/home/z/user/qemu/Avnet-Digilent-ZedBoard-2015.4/images/linux# petalinux-util --gdb vmlinux
    GNU gdb (Sourcery CodeBench Lite 2015.05-17) 7.7.50.20140217-cvs
    Copyright (C) 2014 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-xilinx-linux-gnueabi".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    <https://sourcery.mentor.com/GNUToolchain/>.
    Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.
    For help, type "help".
    Type "apropos word" to search for commands related to "word"...
    Reading symbols from vmlinux...(no debugging symbols found)...done.
    (gdb) target remote :9000
    Remote debugging using :9000
    Ignoring packet error, continuing...
    warning: unrecognized item "timeout" in "qSupported" response
    Ignoring packet error, continuing...
    Ignoring packet error, continuing...
    Bogus trace status reply from target: timeout
    (gdb) target remote :1534
    :1534: Connection timed out.
    (gdb) target remote :907 
    :907: Connection timed out.
     
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • chenzhenyuch
    0 chenzhenyuch over 8 years ago in reply to jafoste4

    Have you had any comment?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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