Forum - Recent Threads

another critical bug in OpenSSL

JWx — Thu, 19 Feb 2026 11:12:44 GMT

It seems that we have another remote code execution in recent OpenSSL versions (CVE-2025-15467), this time in AEAD component.

Debian advisory is here. From openssl advisory it seems that it mainly affects less popular use-cases

Applications and services that parse untrusted CMS or PKCS#7 content using
AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.
Because the overflow occurs prior to authentication, no valid key material
is required to trigger it. While exploitability to remote code execution
depends on platform and toolchain mitigations, the stack-based write
primitive represents a severe risk.

chipkit_pi.zip

mtccomp — Mon, 01 Dec 2025 21:09:37 GMT

Im looking for the link to the software chipkit_pi for the MPIDE can any one point me in the direction

element 14 shows bad header when you look for it or its not found.

Digilent CPLD Development Board Digilab XC2 JTAG

marmotking — Wed, 12 Feb 2025 22:53:56 GMT

I have an old Digilab XC2 CoolRunner II development board which has a 6 pin JTAG header on it. The documentation which is as old as the board says you need a P-3 or P-4 adaptor. I have an HS2 adaptor. It's keyed the same and is also 6 pins. Will this work instead of the P-3 or P-4?

Looking for SBC with Heterogeneous Multicore Processor for Drone Development

sidereal — Wed, 09 Oct 2024 01:21:14 GMT

Hello everyone,
I’m looking for a recommendation on a single-board computer (SBC) that features a heterogeneous multicore processor suitable for drone applications. Here’s what we need:

At least 4 cores in total, with 2 or more being real-time cores
RISC -V core is preferred, ARM is ok
Ability to run Linux on the application cores and boot an RTOS on the real-time cores (Or propose alternative boot sequence)
Not near the end of life, and with decent long-term support
Ideally an SBC (i.e. we do not have to create our own boards from scratch), with Analog and Digital GPIO
Wishful thinking: two ethernet ports (i.e. can act as a bridge) but is not necessary
LCD output greatly appreciated. 4K video,High definition and such not necessary
Wishful thinking: On board Graphics acceleration, If available, should be accessible for GPU programming via a cuda like mechanism

I came across people having success with Toradex and Sifive Unleashed. But I cant find detailed receipe to prepare everything and set up the boards like I want
Any suggestions for hardware that fits this description would be greatly appreciated! Thanks in advance! [xposting on askelectronics]

Anyone have any go-to AI tools for hardware design yet?

Kirchoff1010 — Tue, 06 Aug 2024 21:36:35 GMT

I stumbled across www.Zenode.AI the other day and it's pretty cool tool for reading component datasheets (at least for being free). It made me wonder if anyone other tools exist beyond ChatGPT yet that anyone likes?

installing Lubuntu on an older laptop

Jan Cumps — Sun, 23 Jun 2024 14:26:38 GMT

I have an HP Pavilion laptop from my youngest daughter. I assumed possession when the HD failed and we gave her something else. I was running Ubuntu proper on it, version 20.04. But it was a bit too light to run the gui.

Because I want to use the machine as a native Linux, with some desktop, I am now trying out Lubuntu. Same kernel, same versions. But a lighter distribution. The laptop has a small coprocessor, little memory, but an extremely big (replaced by me) SSD hard disk. I want it to have a gui, because the laptop has a touch display and that makes some activities easier on a graphical screen. But the main work will be command line stuff.

Let's see how this experiment turns out ...

How to write files in littlefs filesystem SPI External flash ?

parthsanepara — Wed, 15 May 2024 07:39:15 GMT

Hi,

I would like to know some techniques or any readily available tools or modules available in the market. to write for ex. .txt, .mp3 files in my external used with my Host MCU via SPI Flash (Winbond). For flash file management I am using littlefs file system. I can able to access the filesystem within MCU access. but I want to write some large files with host PC before mounting flash on the PCB.

Thanks,

Parth

EV_ICM-42605

cupracing — Sun, 14 Jan 2024 10:41:28 GMT

Hello, anyone has the datasheet or an electrical scheme of this board?

I am trying to communicate with that board with an esp32wrom devkit but i am not able to do anything. So i want be sure i am connecting or powering on it right

Thanks

Letter of Volatility for PN AES-Z7MB-7Z010-SOM-G/AES-Z7MB-7Z020-SOM-G

edgargortiz — Thu, 18 May 2023 00:12:34 GMT

I am trying to see if someone can help provide a Letter of Volatility (LOV) for the MicroZED boards PN: AES-Z7MB-7Z010-SOM-G/AES-Z7MB-7Z020-SOM-G.

The LOV identifies all memory types and memory size, as well as how to sanitize/clear the memory.

Use ranges with the product search API

david_gomez — Sat, 15 Apr 2023 21:26:44 GMT

I'm working right now on a collage project where I want to list certain components available at Element14 using the product search API to get them.

The specific issue I have is figuring out how to use the keyword search to filter as much as I can the results I will get from the API, an specific example can be looking for inductors with an inductance with a minimum 90uh and a maximum of 110uh.

I don't know how to build the query URL (specifically the `term:any` param) for the API to return me the data I can get using the website filters.

Is there more in depth documentation on how to build the keyword search somewhere?

Can anybody with more experience using the API help me to understand if there is a better way to achieve what I need?

Thank you in advance for any help you can provide.

AES-ZU-RFSOC-SK-RVS-G Zynq UltraScale+ RFSoC Development Kit with LTE RF Front End

Former Member — Fri, 09 Sep 2022 19:47:43 GMT

AES-ZU-RFSOC-SK-RVS-G

Request for order

Former Member — Thu, 08 Sep 2022 10:01:46 GMT

Hello for All

Im working here for an project and I need to buy

mmWave SDR with specification as below

Radio front end:
4-channel fully-digital transceiver board
Operating frequency: 57-64 GHz band
Bandwidth: ~2GHz
1X4 ULA Array Antennas at the TX and RX side
•Xilinx Zynq® UltraScale+™ RFSoC ZCU111 Evaluation Kit
•Installation and training included
•Warranty: 1 year

Please let me know any one where I can order or who can support for order for this equipment because manufacturer does not accept to sell outside USA

We can accept any mmWave that can meet specification or is equivalent

Best Regards

Which Development board to buy

mehdimoore — Mon, 28 Feb 2022 17:35:18 GMT

Hi All,

I have recently joined the forum but I hope I am writing the question in right forum!

I am going to buy a Xilinx FPGA development board (SOM) but I am not sure which one. I will use the board for testing/accelerating simulations of some particular DSP algorithms. For example I have implemented a 5G compliant LDPC decoder in Verilog and I want to test it on FPGA now. My application is mostly about sending data from PC to the board, do DSP processing, and then send the results back to PC. I don't need fancy peripherals so even a working USB port is enough for my work (I don't want to spend much of money on a board with numerous peripherals that I am not going to use)

my basic requirements are:

- about 300k-500k LUTs

- 1 peripheral with PC (e.g., USB, Ethernet, etc)

Due to my budget I would like to consider the cheapest options.

Any suggestion is greatly appreciated.

Mehdi

Where can I order MicroZed AES-Z7MB-7Z020-SOM-G/REV-H now? urgently!

patlin — Fri, 19 Nov 2021 19:58:43 GMT

Hi, Dear Sir or Madam,

Does any one in community know Where I can order MicroZed AES-Z7MB-7Z020-SOM-G/REV-H now? It shows out of stock, but our team needs it urgently.

Thanks in advance for any help!

Patrick

Hirose DF11 : 2.0mm Pitch, Double-Row Connector (UL/CSA Complaint)

t.adegoke — Tue, 02 Nov 2021 16:17:55 GMT

HIROSE'S DF11 FEATURES:

1. Space-saving

2. Available in Wide Varieties

3. Wide Applicable Wire Range

4. IDC Type enabling reduced assembly time

Check out our products: https://uk.farnell.com/w/search/prl/results?brand=hirose-hrs&product-range=df11-series&ost=hirose%20df11

Are you looking for a waterproof & miniature waterproof circular connector?

t.adegoke — Fri, 23 Jul 2021 11:33:49 GMT

Would Hirose's HR30 Series be suitable for your applications?

Our HR30 series are miniature waterproof plastic circular connectors that meet the requirement for outdoor electronic equipment.

The range consists of lightweight and small size plastic plugs, (including overmold type), receptacles, jacks, and accessories. Many varieties are available; the 3 and 6 contact versions are in a 12.6 mm diameter shell and the 10 and 12 contact versions are in a 15.5 mm diameter shell to give design flexibility. Further options include solder bucket, crimp, or through-hole contacts.

The innovative connector design incorporates gaskets, seals, and built-in strain relief to give IP67 or IP68 rated protection from dust and water penetration.

The user-friendly push-pull locking mechanism securely locks the mated connectors which are confirmed by an audible click. The connectors are simply pushed together and then quickly and easily disconnected by pulling on the plug’s release collar which has grooves to aid with the grip of the connector. Furthermore, visual white arrow alignment indicators and multiple polarizing keys ensure correct alignment and mating engagement. Minimal tooling is required for the simple assembly of the plug.

Ideal applications are servo motors, FA robots, GPS devices, measurement devices, LED lighting, and many more.

For more information click the below links:

HR30 series - HIROSE Electric Group [Connector]

https://nl.farnell.com/search?st=hirose%20hr30

Attachments:

community.element14.com/.../HR30-Series_5F00_PR.pdf

HR30 Series_PR.pdf

Looking for RFID hardware and software insight

colporteur — Tue, 25 May 2021 17:23:47 GMT

I am looking at pursuing some security research into RFID cards. I would like to be able to read and replicate lower freq and mid freq cards. My focus is more on the mid freq cards but the lower freq cards can provide some insight. I have watched a few youtube videos to get some idea of what is involved. I have found a myriad of hardware options and mostly Proxmark for software.

I'm looking for insight into hardware and software recommendation that support a working solutions?

I'm looking for insight into operating system that supports a working solutions?

I'm looking for insight into a working solutions using Raspberry Pi and Arduino?

I'm looking for insight from a person that has a working solutions and not heard about or seen about it. Getting it to work from bare metal ,to me provides experience. I'm looking to tap that experience. My goal is to get a working solution. I am willing to invest the time to get to that point but, I am trying to avoid the numerous dead ends I would follow if I did it on my own, to get it working. You could try this or you could try that if it fails, is not what I am looking for.

My immediate need is the working setup for the research project, not really the journey through the valley of learning to get there. What I need to learn will be done in the working solutions, at least I hope.

Petalinux SDK to avnet uz3eg_iocc

bi̇rsen — Fri, 16 Apr 2021 07:50:12 GMT

Hi,

Can I ask a question about petalinux?

I use avnet uz3eg_iocc board.

Vivado 2018.3 peyalinux 2018.3.

I created a petalinux project by using my vivado hdf file that is basic project . There are gpıo and LED is blinked.

I boot from SD card. After gpıo export, my led that is on the avnet board blinks.

My question is : How can I add SDK source file in my petalinux project ?

what I mean is that there are some source file in SDK, PS part, How can I these to my petalinux project ?

For example in SDK I write C code that is press the button and the led blinks.

how can Iadd this to the petalinux project ?

Thank you for your help

96Boards Dual Camera Mezz Out of Box image - failed to find mode "1920x1080" for connector 42

jomoenginer — Wed, 17 Mar 2021 06:53:34 GMT

I have been attempting to run the Out of Box image as per the 96Boards Dual Camera Mezz Getting Started Guide, but I keep getting an error and no image is displayed on the screen. I have rebooted the board while connected to a monitor and still no luck.

Any suggestions on how to resolve this?

Ref:

Getting Started Guide

96Boards_Dual_Camera_Mezz_GSG.pdf

96Board Dual Camer Mezz page with Out of Box Image

96Boards ON Semiconductor Dual Camera Mezzanine | element14 | Design Center

I've tried this with multiple Monitors as well as connecting to a TV, but I get the same error:

root@ultra96v2-2020-1:~# run_1920_1080
725
failed to find mode "1920x1080" for connector 42
failed to create dumb buffer: Invalid argument
testing 1920x1080@YUYV overlay plane 38
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstKMSSink:kmssink0: Could not get allowed GstCaps of device
Additional debug info:
../../../git/sys/kms/gstkmssink.c(1102): gst_kms_sink_start (): /GstPipeline:pipeline0/GstKMSSink:kmssink0:
driver does not provide mode settings configuration
Setting pipeline to NULL ...
Freeing pipeline ...
/usr/bin/run_1920_1080: line 20: kill: (725) - No such process
root@ultra96v2-2020-1:~# t

Boot message:

A Couple of message to note:

xilinx-video amba_pl@0:vcap_csi: Entity type for entity a0020000.mipi_csi2_rx_subsystem was not initialized!

xilinx-video amba_pl@0:vcap_csi: Entity type for entity a0080000.v_proc_ss was not initialized

96Boards Dual Camera Mezz Out of Box image error


[    2.990368] rtc_zynqmp ffa60000.rtc: registered as rtc0
[    2.995093] i2c /dev entries driver
[    2.999107] xilinx-video amba_pl@0:vcap_csi: device registered
[    3.004837] xilinx-csi2rxss a0020000.mipi_csi2_rx_subsystem: Xilinx CSI2 Rx Subsystem device found!
[    3.013283] xilinx-video amba_pl@0:vcap_csi: Entity type for entity a0020000.mipi_csi2_rx_subsystem was not initialized!
[    3.025050] xilinx-tpg a0050000.v_tpg: invalid number of ports 0
[    3.030062] xilinx-tpg: probe of a0050000.v_tpg failed with error -22
[    3.036692] xilinx-vpss-scaler a0080000.v_proc_ss: xlnx,v-vpss-scaler-2.2 - compatible string is getting deprecated!
[    3.046994] xilinx-video amba_pl@0:vcap_csi: Entity type for entity a0080000.v_proc_ss was not initialized!
[    3.056618] xilinx-vpss-scaler a0080000.v_proc_ss: Num Hori Taps 8
[    3.062754] xilinx-vpss-scaler a0080000.v_proc_ss: Num Vert Taps 8
[    3.068895] xilinx-vpss-scaler a0080000.v_proc_ss: VPSS Scaler Probe Successful
[    3.076300] xilinx-vtc a0060000.v_tc: device found, version 6.020
[    3.082283] usbcore: registered new interface driver uvcvideo

Full Boot Message

Xilinx Zynq MP First Stage Boot Loader 

Release 2020.1   Aug 14 2020  -  22:53:13
NOTICE:  ATF running on XCZU3EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE:  BL31: v2.2(release):v1.1-5588-g5918e656e
NOTICE:  BL31: Built : 22:34:55, Aug 14 2020


U-Boot 2020.01 (Aug 18 2020 - 17:33:39 +0000)

Model: Avnet Ultra96 Rev1
Board: Xilinx ZynqMP
DRAM:  2 GiB
PMUFW:    v1.1
EL Level:    EL2
Chip ID:    zu3eg
NAND:  0 MiB
MMC:   mmc@ff160000: 0, mmc@ff170000: 1
In:    serial@ff010000
Out:   serial@ff010000
Err:   serial@ff010000
Bootmode: SD_MODE
Reset reason:    EXTERNAL 
Net:   No ethernet found.
Hit any key to stop autoboot:  2     1     0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2007 bytes read in 20 ms (97.7 KiB/s)
## Executing script at 20000000
8313964 bytes read in 623 ms (12.7 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
   Using 'conf@system-top.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0x100000f4
     Data Size:    8251525 Bytes = 7.9 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00080000
     Entry Point:  0x00080000
     Hash algo:    sha256
     Hash value:   22ed1c58ad614712b771a0e27ff96d52d6b3269321ee423885176b4c41550f32
   Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 10000000 ...
   Using 'conf@system-top.dtb' configuration
   Trying 'fdt@system-top.dtb' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x107dea8c
     Data Size:    60535 Bytes = 59.1 KiB
     Architecture: AArch64
     Hash algo:    sha256
     Hash value:   239f2beeb0c26cfc03521c3c00c8931a234b07770ea13e7fa072f91e0669b391
   Verifying Hash Integrity ... sha256+ OK
   Booting using the fdt blob at 0x107dea8c
   Uncompressing Kernel Image
   Loading Device Tree to 000000000ffee000, end 000000000ffffc76 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.0-xilinx-v2020.1 (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 SMP Tue Aug 18 16:15:52 UTC 2020
[    0.000000] Machine model: Avnet Ultra96 Rev1
[    0.000000] earlycon: cdns0 at MMIO 0x00000000ff010000 (options '115200n8')
[    0.000000] printk: bootconsole [cdns0] enabled
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created DMA memory pool at 0x000000003ed40000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node rproc@3ed400000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 512 MiB at 0x000000005fc00000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 22 pages/cpu s49944 r8192 d31976 u90112
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 515524
[    0.000000] Kernel command line: earlycon console=ttyPS0,115200 clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait cma=512M
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1512432K/2094848K available (11836K kernel code, 690K rwdata, 3684K rodata, 704K init, 516K bss, 58128K reserved, 524288K cma-reserved)
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] random: get_random_bytes called from start_kernel+0x2a8/0x42c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 100.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171024e7e0, max_idle_ns: 440795205315 ns
[    0.000004] sched_clock: 56 bits at 100MHz, resolution 10ns, wraps every 4398046511100ns
[    0.008479] Console: colour dummy device 80x25
[    0.012487] Calibrating delay loop (skipped), value calculated using timer frequency.. 200.00 BogoMIPS (lpj=400000)
[    0.022840] pid_max: default: 32768 minimum: 301
[    0.027602] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.034788] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.043875] ASID allocator initialised with 32768 entries
[    0.047999] rcu: Hierarchical SRCU implementation.
[    0.052944] EFI services will not be available.
[    0.057350] smp: Bringing up secondary CPUs ...
[    0.062090] Detected VIPT I-cache on CPU1
[    0.062137] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.062536] Detected VIPT I-cache on CPU2
[    0.062556] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.062915] Detected VIPT I-cache on CPU3
[    0.062934] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.062984] smp: Brought up 1 node, 4 CPUs
[    0.097142] SMP: Total of 4 processors activated.
[    0.101814] CPU features: detected: 32-bit EL0 Support
[    0.106918] CPU features: detected: CRC32 instructions
[    0.112057] CPU: All CPU(s) started at EL2
[    0.116100] alternatives: patching kernel code
[    0.121618] devtmpfs: initialized
[    0.130505] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.134606] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.156620] xor: measuring software checksum speed
[    0.193587]    8regs     :  2375.000 MB/sec
[    0.233614]    32regs    :  2725.000 MB/sec
[    0.273645]    arm64_neon:  2365.000 MB/sec
[    0.273686] xor: using function: 32regs (2725.000 MB/sec)
[    0.277562] pinctrl core: initialized pinctrl subsystem
[    0.283681] NET: Registered protocol family 16
[    0.288702] DMA: preallocated 256 KiB pool for atomic allocations
[    0.293240] audit: initializing netlink subsys (disabled)
[    0.298660] audit: type=2000 audit(0.240:1): state=initialized audit_enabled=0 res=1
[    0.306304] cpuidle: using governor menu
[    0.310343] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.331356] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.332410] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.339080] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.345739] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    1.426755] DRBG: Continuing without Jitter RNG
[    1.503595] raid6: neonx8   gen()  1546 MB/s
[    1.571612] raid6: neonx8   xor()  1466 MB/s
[    1.639665] raid6: neonx4   gen()  1489 MB/s
[    1.707724] raid6: neonx4   xor()  1430 MB/s
[    1.775803] raid6: neonx2   gen()  1135 MB/s
[    1.843810] raid6: neonx2   xor()  1189 MB/s
[    1.911900] raid6: neonx1   gen()   741 MB/s
[    1.979896] raid6: neonx1   xor()   895 MB/s
[    2.047943] raid6: int64x8  gen()  1166 MB/s
[    2.116021] raid6: int64x8  xor()   763 MB/s
[    2.184086] raid6: int64x4  gen()   984 MB/s
[    2.252113] raid6: int64x4  xor()   740 MB/s
[    2.320199] raid6: int64x2  gen()   684 MB/s
[    2.388220] raid6: int64x2  xor()   600 MB/s
[    2.456265] raid6: int64x1  gen()   453 MB/s
[    2.524301] raid6: int64x1  xor()   460 MB/s
[    2.524343] raid6: using algorithm neonx8 gen() 1546 MB/s
[    2.528293] raid6: .... xor() 1466 MB/s, rmw enabled
[    2.533223] raid6: using neon recovery algorithm
[    2.538631] iommu: Default domain type: Translated 
[    2.542919] SCSI subsystem initialized
[    2.546541] usbcore: registered new interface driver usbfs
[    2.551851] usbcore: registered new interface driver hub
[    2.557124] usbcore: registered new device driver usb
[    2.562169] mc: Linux media interface: v0.10
[    2.566372] videodev: Linux video capture interface: v2.00
[    2.571820] pps_core: LinuxPPS API ver. 1 registered
[    2.576733] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    2.585828] PTP clock support registered
[    2.589723] EDAC MC: Ver: 3.0.0
[    2.593289] zynqmp-ipi-mbox mailbox@ff990400: Registered ZynqMP IPI mbox with TX/RX channels.
[    2.601551] zynqmp-ipi-mbox mailbox@ff90000: Registered ZynqMP IPI mbox with TX/RX channels.
[    2.609801] FPGA manager framework
[    2.613207] Advanced Linux Sound Architecture Driver Initialized.
[    2.619455] Bluetooth: Core ver 2.22
[    2.622680] NET: Registered protocol family 31
[    2.627077] Bluetooth: HCI device and connection manager initialized
[    2.633395] Bluetooth: HCI socket layer initialized
[    2.638237] Bluetooth: L2CAP socket layer initialized
[    2.643259] Bluetooth: SCO socket layer initialized
[    2.648524] clocksource: Switched to clocksource arch_sys_counter
[    2.654281] VFS: Disk quotas dquot_6.6.0
[    2.658095] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    2.669202] NET: Registered protocol family 2
[    2.669672] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    2.677725] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    2.685657] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    2.693156] TCP: Hash tables configured (established 16384 bind 16384)
[    2.699418] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    2.706006] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    2.713193] NET: Registered protocol family 1
[    2.717709] RPC: Registered named UNIX socket transport module.
[    2.723273] RPC: Registered udp transport module.
[    2.727940] RPC: Registered tcp transport module.
[    2.732608] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.739281] PCI: CLS 0 bytes, default 64
[    2.743477] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[    2.750174] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    2.758684] Initialise system trusted keyrings
[    2.762218] workingset: timestamp_bits=46 max_order=19 bucket_order=0
[    2.769344] NFS: Registering the id_resolver key type
[    2.773539] Key type id_resolver registered
[    2.777675] Key type id_legacy registered
[    2.781659] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.788331] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    2.807735] NET: Registered protocol family 38
[    2.807782] Key type asymmetric registered
[    2.810608] Asymmetric key parser 'x509' registered
[    2.815472] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    2.822804] io scheduler mq-deadline registered
[    2.827301] io scheduler kyber registered
[    2.832010] GPIO IRQ not connected
[    2.834665] XGpio: gpio@a0040000: registered, base is 504
[    2.841779] xilinx-frmbuf a0000000.v_frmbuf_wr: Xilinx AXI frmbuf DMA_DEV_TO_MEM
[    2.847433] xilinx-frmbuf a0000000.v_frmbuf_wr: Xilinx AXI FrameBuffer Engine Driver Probed!!
[    2.855954] xilinx-frmbuf a00c0000.v_frmbuf_rd: Xilinx AXI frmbuf DMA_MEM_TO_DEV
[    2.863252] xilinx-frmbuf a00c0000.v_frmbuf_rd: Xilinx AXI FrameBuffer Engine Driver Probed!!
[    2.898012] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.902948] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.909710] brd: module loaded
[    2.915394] loop: module loaded
[    2.916359] mtdoops: mtd device (mtddev=name/number) must be supplied
[    2.920671] libphy: Fixed MDIO Bus: probed
[    2.924372] tun: Universal TUN/TAP device driver, 1.6
[    2.928502] CAN device driver interface
[    2.933150] usbcore: registered new interface driver asix
[    2.937624] usbcore: registered new interface driver ax88179_178a
[    2.943636] usbcore: registered new interface driver cdc_ether
[    2.949430] usbcore: registered new interface driver net1080
[    2.955056] usbcore: registered new interface driver cdc_subset
[    2.960936] usbcore: registered new interface driver zaurus
[    2.966484] usbcore: registered new interface driver cdc_ncm
[    2.973017] usbcore: registered new interface driver uas
[    2.977385] usbcore: registered new interface driver usb-storage
[    2.983509] gadgetfs: USB Gadget filesystem, version 24 Aug 2004
[    2.989815] rtc_zynqmp ffa60000.rtc: registered as rtc0
[    2.994550] i2c /dev entries driver
[    2.998569] xilinx-video amba_pl@0:vcap_csi: device registered
[    3.004283] xilinx-csi2rxss a0020000.mipi_csi2_rx_subsystem: Xilinx CSI2 Rx Subsystem device found!
[    3.012740] xilinx-video amba_pl@0:vcap_csi: Entity type for entity a0020000.mipi_csi2_rx_subsystem was not initialized!
[    3.024495] xilinx-tpg a0050000.v_tpg: invalid number of ports 0
[    3.029518] xilinx-tpg: probe of a0050000.v_tpg failed with error -22
[    3.036142] xilinx-vpss-scaler a0080000.v_proc_ss: xlnx,v-vpss-scaler-2.2 - compatible string is getting deprecated!
[    3.046449] xilinx-video amba_pl@0:vcap_csi: Entity type for entity a0080000.v_proc_ss was not initialized!
[    3.056072] xilinx-vpss-scaler a0080000.v_proc_ss: Num Hori Taps 8
[    3.062211] xilinx-vpss-scaler a0080000.v_proc_ss: Num Vert Taps 8
[    3.068351] xilinx-vpss-scaler a0080000.v_proc_ss: VPSS Scaler Probe Successful
[    3.075752] xilinx-vtc a0060000.v_tc: device found, version 6.020
[    3.081738] usbcore: registered new interface driver uvcvideo
[    3.087379] USB Video Class driver (1.1.1)
[    3.092132] Bluetooth: HCI UART driver ver 2.3
[    3.095861] Bluetooth: HCI UART protocol H4 registered
[    3.100960] Bluetooth: HCI UART protocol BCSP registered
[    3.106252] Bluetooth: HCI UART protocol LL registered
[    3.111340] Bluetooth: HCI UART protocol ATH3K registered
[    3.116715] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    3.122967] Bluetooth: HCI UART protocol Intel registered
[    3.128307] Bluetooth: HCI UART protocol QCA registered
[    3.133513] usbcore: registered new interface driver bcm203x
[    3.139154] usbcore: registered new interface driver bpa10x
[    3.144668] usbcore: registered new interface driver bfusb
[    3.150116] usbcore: registered new interface driver btusb
[    3.155581] usbcore: registered new interface driver ath3k
[    3.161108] EDAC MC: ECC not enabled
[    3.164706] EDAC DEVICE0: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[    3.177173] sdhci: Secure Digital Host Controller Interface driver
[    3.182789] sdhci: Copyright(c) Pierre Ossman
[    3.187113] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.193184] ledtrig-cpu: registered to indicate activity on CPUs
[    3.198758] zynqmp_firmware_probe Platform Management API v1.1
[    3.204503] zynqmp_firmware_probe Trustzone version v1.0
[    3.213383] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: zynqmp pinctrl initialized
[    3.242139] alg: No test for xilinx-zynqmp-aes (zynqmp-aes)
[    3.242397] zynqmp_aes zynqmp_aes: AES Successfully Registered
[    3.242397] 

[    3.249637] alg: No test for xilinx-keccak-384 (zynqmp-keccak-384)
[    3.255846] alg: No test for xilinx-zynqmp-rsa (zynqmp-rsa)
[    3.261416] usbcore: registered new interface driver usbhid
[    3.266637] usbhid: USB HID core driver
[    3.270676] xlnk xlnk: Major 243
[    3.273759] xlnk xlnk: xlnk driver loaded
[    3.277624] xlnk xlnk: xlnk_pdev is not null
[    3.284350] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[    3.288627] usbcore: registered new interface driver snd-usb-audio
[    3.295404] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    3.302632] Initializing XFRM netlink socket
[    3.306266] NET: Registered protocol family 10
[    3.311070] Segment Routing with IPv6
[    3.314348] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    3.320491] NET: Registered protocol family 17
[    3.324520] NET: Registered protocol family 15
[    3.328933] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    3.341802] can: controller area network core (rev 20170425 abi 9)
[    3.347980] NET: Registered protocol family 29
[    3.352356] can: raw protocol (rev 20170425)
[    3.356593] can: broadcast manager protocol (rev 20170425 t)
[    3.362219] can: netlink gateway (rev 20190810) max_hops=1
[    3.367778] Bluetooth: RFCOMM TTY layer initialized
[    3.372521] Bluetooth: RFCOMM socket layer initialized
[    3.377628] Bluetooth: RFCOMM ver 1.11
[    3.381346] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.386608] Bluetooth: BNEP filters: protocol multicast
[    3.391800] Bluetooth: BNEP socket layer initialized
[    3.396728] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.402613] Bluetooth: HIDP socket layer initialized
[    3.407715] 9pnet: Installing 9P2000 support
[    3.411807] Key type dns_resolver registered
[    3.416396] registered taskstats version 1
[    3.420090] Loading compiled-in X.509 certificates
[    3.425316] Btrfs loaded, crc32c=crc32c-generic
[    3.440452] ff000000.serial: ttyPS1 at MMIO 0xff000000 (irq = 40, base_baud = 6249999) is a xuartps
[    3.444433] ff010000.serial: ttyPS0 at MMIO 0xff010000 (irq = 41, base_baud = 6249999) is a xuartps
[    3.458556] printk: console [ttyPS0] enabled
[    3.458556] printk: console [ttyPS0] enabled
[    3.462864] printk: bootconsole [cdns0] disabled
[    3.462864] printk: bootconsole [cdns0] disabled
[    3.472012] of-fpga-region fpga-full: FPGA Region probed
[    3.482959] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
[    3.489571] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[    3.496694] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[    3.503809] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[    3.510926] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[    3.518050] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[    3.525168] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[    3.532286] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[    3.539406] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[    3.546606] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[    3.553721] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[    3.560834] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[    3.567952] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[    3.575070] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[    3.582190] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[    3.589307] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[    3.596424] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[    3.603795] xilinx-psgtr fd400000.zynqmp_phy: Lane:1 type:8 protocol:4 pll_locked:yes
[    3.615655] zynqmp_clk_divider_set_rate() set divider failed for spi1_ref_div1, ret = -13
[    3.624478] xilinx-dp-snd-codec fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0: Xilinx DisplayPort Sound Codec probed
[    3.635213] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[    3.643275] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[    3.651859] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    3.664408] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    3.677133] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: Xilinx DisplayPort Sound Card probed
[    3.687320] OF: graph: no port node found in /amba/zynqmp-display@fd4a0000
[    3.694346] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.700954] [drm] No driver support for vblank timestamp query.
[    3.706966] xlnx-drm xlnx-drm.0: bound fd4a0000.zynqmp-display (ops 0xffffffc010cd78f0)
[    3.846935] random: fast init done
[    7.831159] [drm] Cannot find any crtc or sizes
[    7.835991] [drm] Initialized xlnx 1.0.0 20130509 for fd4a0000.zynqmp-display on minor 0
[    7.844097] zynqmp-display fd4a0000.zynqmp-display: ZynqMP DisplayPort Subsystem driver probed
[    7.854387] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[    7.860943] xilinx-axipmon fd0b0000.perf-monitor: Probed Xilinx APM
[    7.867450] xilinx-axipmon fd490000.perf-monitor: Probed Xilinx APM
[    7.873964] xilinx-axipmon ffa10000.perf-monitor: Probed Xilinx APM
[    7.880980] dwc3 fe200000.dwc3: Failed to get clk 'ref': -2
[    7.886777] xilinx-psgtr fd400000.zynqmp_phy: Lane:2 type:0 protocol:3 pll_locked:yes
[    7.898324] dwc3 fe300000.dwc3: Failed to get clk 'ref': -2
[    7.904106] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:1 protocol:3 pll_locked:yes
[    7.914399] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    7.919892] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    7.927662] xhci-hcd xhci-hcd.0.auto: hcc params 0x0238f625 hci version 0x100 quirks 0x0000000202010010
[    7.937077] xhci-hcd xhci-hcd.0.auto: irq 55, io mem 0xfe300000
[    7.943387] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    7.951658] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.958875] usb usb1: Product: xHCI Host Controller
[    7.963744] usb usb1: Manufacturer: Linux 5.4.0-xilinx-v2020.1 xhci-hcd
[    7.970349] usb usb1: SerialNumber: xhci-hcd.0.auto
[    7.975541] hub 1-0:1.0: USB hub found
[    7.979329] hub 1-0:1.0: 1 port detected
[    7.983476] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    7.988974] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    7.996634] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[    8.003213] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    8.011383] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[    8.019658] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    8.026878] usb usb2: Product: xHCI Host Controller
[    8.031752] usb usb2: Manufacturer: Linux 5.4.0-xilinx-v2020.1 xhci-hcd
[    8.038357] usb usb2: SerialNumber: xhci-hcd.0.auto
[    8.043480] hub 2-0:1.0: USB hub found
[    8.047251] hub 2-0:1.0: 1 port detected
[    8.053063] i2c i2c-0: Added multiplexed i2c bus 2
[    8.057991] i2c i2c-0: Added multiplexed i2c bus 3
[    8.063035] i2c i2c-0: Added multiplexed i2c bus 4
[    8.067977] i2c i2c-0: Added multiplexed i2c bus 5
[    8.073472] tps65086 6-005e: Failed to read revision register
[    8.316537] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    8.469012] usb 1-1: New USB device found, idVendor=0424, idProduct=2744, bcdDevice= 2.21
[    8.477202] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    8.484329] usb 1-1: Product: USB2744
[    8.487982] usb 1-1: Manufacturer: Microchip Tech
[    8.547284] hub 1-1:1.0: USB hub found
[    8.551081] hub 1-1:1.0: 4 ports detected
[    8.611225] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    8.636912] usb 2-1: New USB device found, idVendor=0424, idProduct=5744, bcdDevice= 2.21
[    8.645094] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=0
[    8.652230] usb 2-1: Product: USB5744
[    8.655887] usb 2-1: Manufacturer: Microchip Tech
[    8.691279] hub 2-1:1.0: USB hub found
[    8.695079] hub 2-1:1.0: 3 ports detected
[    8.904531] usb 1-1.4: new high-speed USB device number 3 using xhci-hcd
[    8.922683] i2c i2c-0: Added multiplexed i2c bus 6
[    8.928154] ina2xx_adc 7-0040: error configuring the device
[    8.933829] i2c i2c-0: Added multiplexed i2c bus 7
[    8.938769] i2c i2c-0: Added multiplexed i2c bus 8
[    8.943710] i2c i2c-0: Added multiplexed i2c bus 9
[    8.948513] pca954x 0-0075: registered 8 multiplexed busses for I2C switch pca9548
[    8.956117] cdns-i2c ff030000.i2c: 100 kHz mmio ff030000 irq 30
[    8.963000] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer with timeout 60s
[    8.970506] cdns-wdt ff150000.watchdog: Xilinx Watchdog Timer with timeout 10s
[    9.007198] mmc0: SDHCI controller on ff160000.mmc [ff160000.mmc] using ADMA 64-bit
[    9.015660] sdhci-arasan ff170000.mmc: allocated mmc-pwrseq
[    9.022271] usb 1-1.4: New USB device found, idVendor=0424, idProduct=2740, bcdDevice= 2.00
[    9.030625] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    9.037930] usb 1-1.4: Product: Hub Controller
[    9.042364] usb 1-1.4: Manufacturer: Microchip Tech
[    9.067917] mmc1: SDHCI controller on ff170000.mmc [ff170000.mmc] using ADMA 64-bit
[    9.079546] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    9.086743] rtc_zynqmp ffa60000.rtc: setting system clock to 1970-01-01T00:00:12 UTC (12)
[    9.094923] of_cfs_init
[    9.097394] of_cfs_init: OK
[    9.100372] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    9.116785] mmc0: new high speed SDXC card at address 0001
[    9.122796] mmcblk0: mmc0:0001 00000 59.6 GiB 
[    9.128638]  mmcblk0: p1 p2
[    9.138996] mmc1: new high speed SDIO card at address 0001
[    9.237401] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    9.243932] clk: Not disabling unused clocks
[    9.248194] ALSA device list:
[    9.251151]   #0: DisplayPort monitor
[    9.255278] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    9.263900] cfg80211: failed to load regulatory.db
[    9.304569] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    9.312694] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    9.332092] devtmpfs: mounted
[    9.335362] Freeing unused kernel memory: 704K
[    9.339882] Run /sbin/init as init process
[    9.426708] random: crng init done

INIT: version 2.88 booting

Starting udev
[    9.885600] udevd[165]: starting version 3.2.8
[    9.953910] udevd[166]: starting eudev-3.2.8
[   10.116090] mali: loading out-of-tree module taints kernel.
[   10.122654] AP1302 4-003c: Probe: AP1302
[   10.126772] debugfs: Directory '4-003c' with parent 'regmap' already present!
[   10.166396] zynqmp_r5_remoteproc zynqmp-rpu: RPU core_conf: split
[   10.172958] remoteproc remoteproc0: r5@0 is available
[   10.221737] AP1302 4-003c: AP1302 Chip ID is 0x265
[   10.237426] AP1302 4-003c: AP1302 Chip Rev is 0x206
[   10.242412] AP1302 4-003c: Start to load firmware.
[   10.761329] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   16.670244] [drm] Cannot find any crtc or sizes
[   16.762099] AP1302 4-003c: Load firmware successfully.
[   16.768932] AP1302 4-003c: AP1302 probe Success Done
[   16.843826] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Wed Aug 19 04:06:10 UTC 2020

Starting Ultra96 AP setup daemon.

Turning Ultra96 WiFi & Bluetooth LEDs ON...done.



[   19.260157] wifi_pm : 0
[   19.262692] wifi_pm : 1
Starting Flask server deamon to serve Ultra96 startup page[   19.265752] wilc_sdio mmc1:0001:1: Driver Initializing success
[   19.279223] WILC POWER UP
[   19.281906] wilc_sdio mmc1:0001:1: SDIO speed: 50000000
[   19.287416] wilc_sdio mmc1:0001:1: chipid 003000d0
.


INIT: Entering runlevel: 5


Starting system message bus: dbus.

Configuring network interfaces... Successfully initialized wpa_supplicant

done.

Starting Connection Manager

Starting haveged: haveged: listening socket at 3

haveged: haveged starting up






Starting Dropbear SSH server: dropbear.

Starting rpcbind daemon...done.

starting statd: done

Starting bluetooth: bluetoothd.

Starting internet superserver: inetd.

exportfs: can't open /etc/exports for reading

NFS daemon support not enabled in kernel

Starting ntpd: done

Starting syslogd/klogd: haveged: haveged: ver: 1.9.5; arch: generic; vend: ; build: (gcc 9.2.0 CTV); collect: 128K




haveged: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 11/40; sz: 15456/64452




haveged: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B):  last entropy estimate 7.99804




haveged: haveged: fills: 0, generated: 0 




done

Starting internet superserver: xinetd.

 * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon

 [A [74G[ ok ]

Starting Telephony daemon

Starting watchdog daemon...done

Starting Linux NFC daemon

Starting tcf-agent: OK


PetaLinux 2020.1 ultra96v2-2020-1 ttyPS0

LTspice Cats! Met these?

navadeepganeshu — Mon, 18 Jan 2021 10:10:29 GMT

Found this on LTspice help page. But, wait!

Who are they? Why are they here?

Just curious

Reflash Xplained Evaluation Kit for ATxmega128A1 with bootloader

geshka — Wed, 16 Dec 2020 02:21:02 GMT

Hello there.

I happened to have Xplained Evaluation Kit for ATxmega128A1 board that was previously preprogrammed with some sort of SW which caused to not being recognized with USB port. May be boot-loader was wiped , not sure though. Is there way to reset board to initial condition ?

Est_ce que le logiciel base-1.1.0.deb est compatible avec la dernière version de RaspiOS?

larrey — Mon, 16 Nov 2020 07:58:36 GMT

Bonjour

J'essaie de remettre à jour mon pi 3B avec la nouvelle version de Raspbian. Mais quand j'exécute pidesktop-base.1.1.0.deb je n'ai plus accès au SSD et piclone ne marche pas. Je n'ai pas accès au SSD et je ne peux dupliquer la carte SD. Des solutions?

Cordialement,

Recommended EMC simulation tools and techniques?

waleedelmughrabi — Sat, 03 Oct 2020 15:41:17 GMT

I believe each PCB layout and hardware engineer have his/her own approach to tackle EMC issues. I think using good practice and spending more time in the design phase will save a lot of time later on, especially with designs invloving high frequency clocks and switching power supplies. I am currently looking into investing in an EMC siulation tool to simulate PCB behaviour, one option that seems popular is CST Studio, would appreciate any thoughts and recommendations about this topic.

Some references:

https://www.signalintegrityjournal.com/articles/480-leading-eda-tools-for-emcemi-design-challenges

https://www.mentor.com/pcb/hyperlynx/full-wave-solver/

https://www.keysight.com/gb/en/products/software/pathwave-design-software/pathwave-em-design-software.html

Hack old vending machine touch pad to control LED lights

goatyhead — Wed, 26 Aug 2020 00:02:07 GMT

I am converting an old vending machine into a box you can sit in and i wanted to hack the vending machine touch pad to be able to change the lighting patterns of LED strips i want to mount inside the box. the touch pad has 21 buttons, and a 12 pin attachment. (i attached a photo of it). I am a newbie at electronics and it was hard to even find a place to ask a question like this. Any help will be appreciated.

Attachments:

Thermal Dynamic of foam?

colporteur — Sun, 21 Jun 2020 03:32:36 GMT

When did foam become a good thermal conductor?

I studied electronics when Marconi was developing wireless technology. Well maybe not that far back. My career started on the cusp of the transition from glass transistors to semiconductor transistors. The one course in technical school that I had to pass and stood in the way of me graduating from college was Thermal Dynamics, the design consideration for heat transfer in the electronic components. The instructor was an Engineer and the Dean. I found him a poor instructor and struggled in the course. Our relationship deteriorated the more I struggled. I did mange to graduate. The Dean signed off on my thesis paper to graduate.

I recall it was important to span the air gap between a component and the heat sink. Sizing the heat sink was important but that air gap left unaddressed impacted the design. Liquid thermal compound we called paste was the go to solution. It filled the air gap to increased the thermal conductivity between the components and heat sink. About ten years ago I came across a thermal tape to replace the thermal paste. It was cleaner. Now I discover a foam?

I purchased a knock-off Pi4B metal case that doubles as a heat sink. The air gap between the Pi components and the metal case was close to a 16 of an inch. Wow! Included in the kit was foam pads. More pads (red circle) than required to cover the components that needed a heat sink. I was sceptical it would worked. Using the stress test posted here https://core-electronics.com.au/tutorials/stress-testing-your-raspberry-pi.html I discovered the metal case warms up but Hey it works.

My question to those individuals that never heard of a glass transistor, meaning your learning is newer than mine, on a scale of best to worse thermal conductivity solutions what is used today for bridging the thermal gap?