NANO PI M4V2

-

Useful info for quick understanding, 

 https://wiki.friendlyarm.com/wiki/index.php/NanoPi_M4V2

Debug UART Pins:

 

 

eMMC pins:

 

 

24Pin Extension ports:

2 independent native USB 2.0 Host
PCIe x2 PWM x1, PowerKey


  

 

40Pin GPIO Extension ports:

Three 3V/1.8V I2C, one 3V UART, one 3V SPI, one SPDIF_TX, eight 3V GPIOs

one 1.8V 8 channels I2S


https://wiki.friendlyarm.com/wiki/images/c/c0/NanoPi_M4V2-B01.jpg 


MIPI-CSI Interface Pins:


SoC: Rockchip RK3399

  • CPU: big.LITTLE，Dual-Core Cortex-A72(up to 2.0GHz) + Quad-Core Cortex-A53(up to 1.5GHz)
  • GPU: Mali-T864 GPU，supports OpenGL ES1.1/2.0/3.0/3.1, OpenCL, DX11, and AFBC
  • VPU: 4K VP9 and 4K 10bits H265/H264 60fps decoding, Dual VOP, etc https://wiki.friendlyarm.com/wiki/images/c/c0/NanoPi_M4V2-B01.jpg

https://wiki.friendlyarm.com/wiki/images/0/0f/NanoPi_M4V2_Layout.jpg

Mali gpu is properietry so nothing to learn there, may be learn gpu tests.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Comments

Post a Comment

Popular posts from this blog

dev_get_platdata understanding

-
So I see this type of code in platform driver inside kernel, struct gpio_led_platform_data *pdata = dev_get_platdata(&pdev->dev); or this, struct aat2870_platform_data *pdata = dev_get_platdata(&client->dev); So how dev_ get_platdata is helping us. In device.h the definition here is, static inline void *dev_get_platdata(const struct device *dev) { return dev->platform_data; } So if I see from kernel it is always done for to get platform specific data. Like Here is a definition of platform_device, in platform_device.h struct platform_device { const char *name; int id; bool id_auto; struct device dev;  <-------------------- u32 num_resources; struct resource *resource; const struct platform_device_id *id_entry; char *driver_override; /* Driver name to force a match */ /* MFD cell pointer */ struct mfd_cell *mfd_cell; /* arch specific additions */ struct pdev_archdata archdata; }; further struct devic...
Read more

Getting started with pinctrl subsystem linux

-
A pin controller is a piece of hardware, usually a set of registers, that can control PINs. It may be able to multiplex, bias, set load capacitance, set drive strength, etc. for individual pins or groups of pins.   PINMUX   PINCONF - electronic properties e.g. high impedance, tristate, input pin to VDD or GND using a certain resistor value - pull up and pull down so that the pin has a stable value when nothing is driving the rail it is connected to, or when it’s unconnected. Pin configuration can be programmed by adding configuration entries into the mapping table     say that we have a group of pins dealing with an SPI interface on { 0, 8, 16, 24 }, and a group of pins dealing with an I2C interface on pins on { 24, 25 }.   make a group static const unsigned int spi0_pins[] = { 0, 8, 16, 24 }; static const unsigned int i2c0_pins[] = { 24, 25 }; //combine them  static const struct foo_group foo_groups[] = { { .name = "spi0_grp", ...
Read more

How to take systrace in android

-
Image
Install python 2.7 . As systrace does not support python 3.6. Python has its own package manager 'pip'. Use it to install new packages.         download python2.7 install pywin32 and six module on windows. Open power shell in C:/Python27/Scripts path,          pip install pywin32          pip install six   Above packages are not required to be installed on Ubuntu. But if you want other packages of python, we have to install python-pip, however not required for systrace.           sudo apt install python-pip        Then do pip list to see what packages are installed in Ubuntu. Install android studio        Start android studio from the downloaded android studio. That will        have a script to start an...
Read more