ブログ

キャンセル
次の結果を表示 
次の代わりに検索 
もしかして: 

Blogs

kenli
NXP Employee
NXP Employee

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.

詳細を読む...

件数が多いもの
0 0 46
yipingwang
NXP TechSupport
NXP TechSupport

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

詳細を読む...

件数が多いもの
0 0 910
nxa18344
NXP Employee
NXP Employee

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.

詳細を読む...

件数が多いもの
0 0 1,264
hemantagrawal
NXP Employee
NXP Employee

  • 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

詳細を読む...

件数が多いもの
0 0 1,452
michelle
NXP Pro Support
NXP Pro Support

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:

詳細を読む...

件数が多いもの
1 2 3,184