Hey everyone!! This one is going to be a very brief blog. A lot of times, system developers encounter OOPS from the linux kernel while tweaking in the kernel drivers.
A kernel OOPS is a non-fatal but serious error that help developers debug the potential problems.
It is like the kernel is the patient with an illness trying to talk to a doctor and telling what is wrong with it so that the developers can identify the issue and fix it.

It generally occurs when the kernel detects an invalid operation such as an illegal memory access, NULL pointer dereferences, invalid instruction execution. An OOPS doesn't necessarily mean that the system will stop working right there and then. However, it does impact the reliability of the system until a point at which the system could potentially halt and stop working.

Hello to you all! In this blog, we will focus on low power management in PCIe. PCIe Power management aims at reducing power consumption in PCIe devices by putting them to low power states when they are idle and bringing them back to full power state when required.

Why does it matter ?  Because PCIe devices in the market such as graphic cards, storage devices, Network Interface Cards can consume significant power when they are active. Power management allows them to scale down their power consumption during idle or periods of low activity.

Hey everyone! This blog will cover the following: -

1. System Overview
2. Use-case
3. What are Outbound and Inbound windows in PCIe and how do they work?
4. What is ATU and why is it important in PCIe?
5. How to configure the PCIe windows in LS1028 and iMX8QXP
6. Code walkthrough
7. Running the test case

Security is becoming more and more important in automotive products and related designs. The attachment shows how to perform simple verification of the secure boot process based on LSDK2108 and LX2160ARDB.

1.     Debugging Packet Loss Issue

1.1 Frame Manager(FMan) Introduction

1.2 Frame Manager Buffer Manager Interface (BMI) Rx Port Statistics Counters

1.3 Linux Sysfs Support for Fman Rx Port Statistics

2.     Queue Manager(Qman) Enqueue Rejections

2.1 Reasons for an Enqueue Rejection

2.2 Frame Queue Descriptor

2.3 Qman Debugfs

2.4 Buffer Manager (BMan) Debugfs

SPDK (Storage Performance Development Kit) is an optimized storage reference architecture. It is initiated and developed by Intel.

SPDK provides a set of tools and libraries for writing high performance, scalable, user-mode storage applications. It achieves high performance by moving all of the necessary drivers into userspace and operating in a polled mode, like DPDK.

• Disable hw_prefetch (u-boot):

setenv hwconfig 'fsl_ddr:bank_intlv=auto;core_prefetch:disable=0xFE'

qixis reset altbank (reset the board - in case using bank 0 run 'qixis reset' only)

• bootargs or othbootargs - add below parameters to bootargs (u-boot).

                  Make sure you see the same in ‘cat /proc/cmdline’ once kernel is booted:

- use 1G hugepages:

default_hugepagesz=1024m hugepagesz=1024m hugepages=6 (or any number)

- isolate cpu's for user space (for the CPUs running DPDK without kernel interference):

isolcpus=1-7

- make sure no rcu stalls and watchdog prints:

nmi_watchdog=0 rcupdate.rcu_cpu_stall_suppress=1

How to Uboot...  I thought I would write this up as many developers using Layerscape, QoriQ and Qonverge devices will start with a boot loader as the first access to their own newly minted hardware.  There are two paths here.  The first is to get our SDK and find the uboot source in that, modify it as needed.  This is time consuming as you need to build an image to have Yocto pull the source code, and you need to jump through some hoops to rebuild with yocto after making your own custom uboot. 

The second is to go straight to the git repo, pull it and build with the cross compiler toolchain that seems most appropriate.  This can be easier in general...  To do this: