@sinovoip wrote:

BPI-Webduino:bit board

webduino bit 1.JPG752x537 63.3 KB

BPI-Webduino:bit interfact:

webduino bit 7.JPG750x1035 88.4 KB

webduino bit 6.JPG750x345 61.2 KB

webduino blockly:

blockly-mac-en.jpg962x549 65 KB

webduino official website:

Posts: 1

Participants: 1

Read full topic

@sinovoip wrote:

BPI R18 Allwinner SoC-Only 3-Mic Far-Field Dev Kit image 20180131

google driver download link:

https://drive.google.com/file/d/1w6HukOJ6cda9jBFJuRxDF6GM6qUjc_p5/view?usp=sharing

baidu cloud download link:

https://pan.baidu.com/s/1bqUqRTH

Posts: 1

Participants: 1

Read full topic

@nathan wrote:

I have a custom board based on BPI-M3, i would like to have a customized uboot and kernel based on Raspbian Pi. I have followed https://www.raspberrypi.org/documentation/linux/kernel/building.md to build the kernel (device tree structure) , but for uboot i am stuck. Any suggestions or links to any similar topics will help me a lot. Thanks

Posts: 1

Participants: 1

Read full topic

@Adam_B wrote:

Hi, I’m looking for any information about USB OTG PHY which is used in Allwinner R40. I’m interested mainly in PHY spec (register list and their descriptions). Anyone can help with this?

Posts: 1

Participants: 1

Read full topic

@etyrnal wrote:

What’s with the price gouging we’re seeing around the web lately?

I’ve seen prices like $279, and $189, and $120. Why are these prices so high?

Posts: 1

Participants: 1

Read full topic

@lost68er wrote:

Hello everybody! I wanted to install Android 5 HDMI on my BPI-M3 today. First I inserted the SD card and started the thing. Everything fine. Then I wanted to connect the device to my PC to install Android with PhoenixSuit on the eMMc memory. My PC did not recognize the M3. When I wanted to start again from the SD card, nothing happened anymore. When I insert the power cable (2.4A), the red LED lights up and nothing else happens. Even if I insert a different image, nothing happens, only the red LED lights up. If I press the power switch for a long time, the red LED goes off. If I press it again, it will light up again, but that’s all. Am I getting into any debugging mode? How can I get out of this? Can someone help?

lost

Posts: 1

Participants: 1

Read full topic

@etyrnal wrote:

BPI-M3 vs M64 – best performance for running Ubuntu Mate ?

Which BPI is more capable for running Ubuntu Mate (to eventually run a headless PlesMediaServer plus Airsonic music server plus low demand NAS?

Eight cores means more simultaneous threads and a higher proc GHz speed… but only 32bit??

64bit proc running at a slower speed with fewer cores feels more ‘future-proof’ – but would it be faster for running the desktop (for the purposes of setup/vnc to machine for administration), and would there be any significant advantage over the faster 8 core processor? Seems like no, but what am i missing?

Posts: 1

Participants: 1

Read full topic

@etyrnal wrote:

BPI-M3 vs M64 – best performance for running Ubuntu Mate ?

Which BPI is more capable for running Ubuntu Mate (to eventually run a headless PlesMediaServer plus Airsonic music server plus low demand NAS?

Eight cores means more simultaneous threads and a higher proc GHz speed… but only 32bit??

64bit proc running at a slower speed with fewer cores feels more ‘future-proof’ – but would it be faster for running the desktop (for the purposes of setup/vnc to machine for administration), and would there be any significant advantage over the faster 8 core processor? Seems like not likely, but what am i missing?

Posts: 1

Participants: 1

Read full topic

@yelvlab wrote:

BPI-Webduino:bit

Development environment：Atom+PlatformIO（Visual Studio Code+PlatformIO）

Need to install ESP32 platform and WS2812 driver library

PIO_platforms.jpg1105x182 17.3 KB

PIO_llibraries.jpg1112x200 28.3 KB

Code

//BPI - BIT test code
#include <Arduino.h>
#include <NeoPixelBus.h>
#include "WiFi.h"

const char* ssid     = "SSID";
const char* password = "PASSWD";

const uint16_t PixelCount = 25;
const uint8_t PixelPin = 4;

#define colorSaturation 64
#define delay_ms 500

NeoPixelBus<NeoGrbFeature, Neo800KbpsMethod> strip(PixelCount, PixelPin);

RgbColor red(colorSaturation, 0, 0);
RgbColor green(0, colorSaturation, 0);
RgbColor blue(0, 0, colorSaturation);
RgbColor white(colorSaturation);
RgbColor black(0);

HslColor hslRed(red);
HslColor hslGreen(green);
HslColor hslBlue(blue);
HslColor hslWhite(white);
HslColor hslBlack(black);

#define AD10 36
#define AD13 39
#define AD14 32
#define AD15 33
#define AD16 34
#define AD17 35

int AD_Value0 = 0;
int AD_Value3 = 0;
int AD_Value4 = 0;
int AD_Value5 = 0;
int AD_Value6 = 0;
int AD_Value7 = 0;

int a = 0;
int w = 0;

void setup()
{
 Serial.begin(115200);
  while (!Serial); // wait for serial attach

  Serial.println();
  Serial.println("Initializing...");
  Serial.flush();

  // this resets all the neopixels to an off state
  strip.Begin();
  strip.Show();


Serial.println();
Serial.println("Running...");
}

void loop()
{
  Serial.println("ADC test!!!");
  for (a = 0; a < 3; a++)
  {
  // turn the LED on (HIGH is the voltage level)
  AD_Value0 = analogRead(AD10);
  AD_Value3 = analogRead(AD13);
  AD_Value4 = analogRead(AD14);
  AD_Value5 = analogRead(AD15);
  AD_Value6 = analogRead(AD16);
  AD_Value7 = analogRead(AD17);

  Serial.println();
  Serial.println("----AD Pin Test----");

//AD10-Pin:IO36
Serial.print("AD10:");
Serial.print(AD_Value0);
Serial.println();

//AD13-Pin:IO39
Serial.print("AD13:");
Serial.print(AD_Value3);
Serial.println();

//AD14-Pin:IO32
Serial.print("AD14:");
Serial.print(AD_Value4);
Serial.println();

//AD15-Pin:IO33
Serial.print("AD15:");
Serial.print(AD_Value5);
Serial.println();

//AD16-Pin:IO34
Serial.print("AD16:");
Serial.print(AD_Value6);
Serial.println();

//AD17-Pin:IO35
Serial.print("AD17:");
Serial.print(AD_Value7);
Serial.println();

Serial.println("----Test Over----");
Serial.println();
delay(2000);
}

Serial.println("LED test!!!");
int l = 0;
for (l = 0; l < 3; l++)
{
int i;

delay(delay_ms);
Serial.println("Colors R");
for (i = 0; i <= PixelCount-1; i++)
{
  strip.SetPixelColor(i, hslRed);
  strip.Show();
}

delay(delay_ms);
Serial.println("Colors B");
for (i = 0; i <= PixelCount-1; i++)
{
  strip.SetPixelColor(i, hslBlue);
  strip.Show();
}

delay(delay_ms);
Serial.println("Colors G");
for (i = 0; i <= PixelCount-1; i++)
{
  strip.SetPixelColor(i, hslGreen);
  strip.Show();
}


  delay(delay_ms);
Serial.println("Colors W");
for (i = 0; i <= PixelCount-1; i++)
{
  strip.SetPixelColor(i, hslWhite);
  strip.Show();
}

  delay(delay_ms);
  Serial.println("Turn Off");
  for (i = 0; i <= PixelCount-1; i++)
  {
    strip.SetPixelColor(i, hslBlack);
    strip.Show();
  }
}
Serial.println("Wi-Fi test!!!");
Serial.print("Connecting to ");
Serial.println(ssid);

WiFi.begin(ssid, password);

while (WiFi.status() != WL_CONNECTED) {
     delay(500);
     Serial.print(".");
   }

Serial.println("WiFi connected"); 
Serial.println("IP address: ");
Serial.println(WiFi.localIP());
Serial.println("Setup done");
Serial.println("");

for (w = 0; w < 3; w++)
{
Serial.println("scan start");

// WiFi.scanNetworks will return the number of networks found
int n = WiFi.scanNetworks();
Serial.println("scan done");
if (n == 0) {
    Serial.println("no networks found");
} else {
    Serial.print(n);
    Serial.println(" networks found");
    for (int j = 0; j < n; ++j) {
        // Print SSID and RSSI for each network found
        Serial.print(j + 1);
        Serial.print(": ");
        Serial.print(WiFi.SSID(j));
        Serial.print(" (");
        Serial.print(WiFi.RSSI(j));
        Serial.print(")");
        Serial.println((WiFi.encryptionType(j) == WIFI_AUTH_OPEN)?" ":"*");
        delay(10);
    }
}
Serial.println("");

// Wait a bit before scanning again
delay(2000);}
WiFi.disconnect();}

• After compiling pass, connect BIT board to the computer, download into BIT board. The program will run automatically, three ADC acquisition first analog signal, and then three LED tests, the color sequence of Red, Green, Blue, white, Black. Then it will connect to WiFi before performing WiFi scanning. You can also block Wi-Fi connection to perform WiFi scanning directly, and print the scanned WiFi signal names in the order of their intensity.

• Test results return View method:

Serial port 115200-8-N-1 settings like, will show the results of each step of the test

Demo Video:Banana pi BPI-webduino:bit function demo

Posts: 1

Participants: 1

Read full topic

@ronfa wrote:

BPI-M2 Zero It’s just a short while I have the board and I would like to use it as a music player with audio output by usb DAC. The question is: in addition to "BPI-M2 zero new image: 2017-12-04-Armbian-5.36-m2-zero-Ubuntu-xenial-next-4.14.3-desktop-preview-buildbybpi" there is there another image like Volumio just for audio? Regards Guido from Italy

Posts: 1

Participants: 1

Read full topic

@charlie wrote:

Hello all, I’m pleased to say I recently bought an M3 board primarily because I wanted something with a few more features and more grunt than a Pi3 while still being able to run a version of Raspbian. I’ve run in to an issue, and I’ll be frank I’m not that great with Linux so some hand-holding may be needed:

When Raspbian boots to the desktop it claims there is no bluetooth adaptor to be found and no wireless interfaces either! I’ve gone through the rigmarole of trying the set wifi up manually as per this link:

and tried the raspi-config option to “wait for network connection during boot” just to see if that would help, even tried to disable power management to see if that would help - sadly, no. When queried the Pi stubbornly reports there is no Wifi or Bluetooth hardware available!

At this point I wondered: -Corrupt installation to SD -Broken hardware Other…? I’ve tried all the versions or raspbian available on the website with the same result, but for the 2016-07-12-raspbian-lite-bpi-m3.img which actually works fine! -Good, not a damaged board… …so I tried the usual process for updating Raspbian and adding ‘X’ and LXDE, but while my connection was working fine many of the files reported “not found” errors. I guess the M3 version of raspbian is sufficiently different you can’t actually do this.

So I’m stuck: -I’ve proven that my M3 is fully functional -But I can’t persuade it to recognise it has wifi (or bluetooth) with any of the versions of Raspbian available that I would find useful to my needs, and can’t seem to update the (for me) functioning lite version.

Out of despiration I wiped the whole /boot directory on the version of raspbian I wanted to use and copied the ‘lite’ version files in in case I was missing a driver… it’s still booted fine, but still no wifi (or bluetooth)

Can anyone suggest what I try next? (no, not another OS as my specific needs require I use a version of Raspbian)

Many thanks, Charles

Posts: 2

Participants: 1

Read full topic

@chaotaklon wrote:

I successfully built and install it on CentOS for BPI-R2. But it gives the following message:

Unable to determine hardware version. I see: Hardware: Mediatek Cortex-A7 (Device Tree)

• expecting BCM2708 or BCM2709 or BCM2835 If this is a genuine Raspberry Pi then please report this to projects@drogon.net. If this is not a Raspberry Pi then you are on your own as wiringPi is designed to support the Raspberry Pi ONLY.

Any way to solve?

Posts: 1

Participants: 1

Read full topic

@mariaczi wrote:

Hello. I recompiled the kernel image to have SATA and RAID support built-in. Now, when I try to copy MBR, partition table and BOOT partition data only, rest to SATA drive (rootfs) I made:

• enter the uboot prompt and change pratition config: emmc pconf 48
• reset to boot OS from SD Card
• enable write mode: echo 0 > /sys/block/mmcblk1boot0/force_ro
• write preloader to EMMC: bpi-bootsel BPI-R2-EMMC-boot0-DDR1600-0k-0905.img.gz /dev/mmcblk1boot0
• copy partition table: sfdisk -d /dev/mmcblk1 | sfdisk -f of=/dev/mmcblk1
• copy MBR from SD card to eMMC: dd if=/dev/mmcblk0 of=/dev/mmcblk1 bs=512 count=1
• copy BOOT partition data: dd if=/dev/mmcblk0p1 of=/dev/mmcblk1p1
• change root partition point in uEnv.txt file on BOOT partition (/dev/mmcblk1p1)
• save and reboot and boot process hang on [BLDR] jump to 0x81E00000 [BLDR] <0x81E00000>=0x0 [BLDR] <0x81E00004>=0x0

What I should do to could copy only the BOOT partition on eMMC and boot successfully from it.

When I copy full XXX.img to eMMC everything works as should, but I can’t waste a time for copying rootfs twice

Regards.

Posts: 2

Participants: 1

Read full topic

@frank-w wrote:

Hi,

can anybody instruct me how to build a new Kernel for first Bananapi

frank@bananapi:~$ uname -r
3.4.113-bananian

frank@bananapi:~$ cat /proc/cpuinfo 
Processor	: ARMv7 Processor rev 4 (v7l)
processor	: 0
BogoMIPS	: 2008.24

processor	: 1
BogoMIPS	: 2015.48

Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xc07
CPU revision	: 4

Hardware	: sun7i
Revision	: 0000
Serial		: 0541920d514848488048578816516647

frank@bananapi:~$ ls /boot/
config-3.4.108-bananian      modes.txt                    System.map-3.4.113-bananian  vmlinuz-3.4.108-bananian
config-3.4.113-bananian      System.map-3.4.108-bananian  ucat.save                    vmlinuz-3.4.113-bananian

actually i’m using 3.4.113-bananian (last bananian release) i have there the config, but my experience with R2 shows that there is a DTB appended and the zImage is used…since the image on bananian is called vmlinuz-3.4.113-bananian and i’ve found no uenv.txt i have no glue if dtb is appended (possible before 4.x??) and how to instruct bootloader (uboot??) to use my own kernel

i don’t want to setup a full new system…only a newer Kernel

regards Frank

Posts: 1

Participants: 1

Read full topic

@sinovoip wrote:

BPI-M2 zero new image: RetroPie for Banana Pi M2 Zero v.1.2.1 beta

Posts: 2

Participants: 1

Read full topic

@Paniez wrote:

Hi all, I just buy a BPI-R2 to put an IPFire. As it doesn’t work, I search some help.

At this point, I think my BPI-R2 with SDCard (Sandisk 32Gb c10) works well (I put kali image and, when I boot, LEDs change - I haven’t HDMI connection).

Now, I put IPFire image (ARM with serial console), but nothing appends : I have 3 RGB LEDs on and nothing. So, if someone have an idea.

Thanks

Posts: 2

Participants: 2

Read full topic

@wtolkien wrote:

Hi everyone:

I wanted to announce the availability of a Yocto / OpenEmbedded layer for the MT7623 here: meta-mediatek.

For those who don’t know, OpenEmbedded is a modular build system to create Linux distributions for various target platforms with a strong focus on embedded devices. It is not a complete distribution or a router platform such as LEDE, but merely a framework to create such a distribution.

Unfortunately I only have a generic Mediatek MT7623 eval board and not an actual BPI-R2. I figured this might still be useful to some people here.

And if Sinovoip is able to provide an R2, I’m more than happy to add support for it!

The long term goal is to port VyOS to this platform. I have also started an OpenEmbedded VyOS layer but there is still a lot of work to do.

Feedback and help is always welcome!

(And Happy Chinese New Year to everyone in Asia!)

Wolfgang

Posts: 2

Participants: 2

Read full topic

@meg wrote:

Hi,

Is there a way to get the average room light level from the camera ? And is it possible to have ‘the last picture’ of the camera ? on the SD I only have the AVI, no JPG.

Thanks Meg

Posts: 1

Participants: 1

Read full topic

@arkhipenko wrote:

So I bought this adapter: Nano 150M Banana Pi WiFi USB 2.0 Dongle (here) because it says Banana Pi. So one would assume it works with all Banana Pi’s. No such luck: 3.4.39-BPI-M3-Kernel does not have appropriate module included.

USB device ID: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

I found the kernel source: here I found the required module source: rtl8188eu

It compiles almost to the end, but then it breaks:

root@bpi-iot-ros-ai:~/workspace/RTL8188EU/rtl8188eu# make
make ARCH=arm CROSS_COMPILE= -C /lib/modules/3.4.39-BPI-M3-Kernel/build M=/home/pi/workspace/RTL8188EU/rtl8188eu  modules
make[1]: Entering directory '/media/mikey/BPI-USER/github/build/release/BPI-M3-bsp/linux-sunxi'

  WARNING: Symbol version dump /media/mikey/BPI-USER/github/build/release/BPI-M3-bsp/linux-sunxi/Module.symvers
           is missing; modules will have no dependencies and modversions.

  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_ap.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_br_ext.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_cmd.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_debug.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_efuse.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_ieee80211.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_io.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_ioctl_set.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_iol.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_led.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_mlme.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_mlme_ext.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_mp.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_mp_ioctl.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_pwrctrl.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_p2p.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_recv.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_rf.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_security.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_sreset.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_sta_mgt.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_wlan_util.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/core/rtw_xmit.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/HalHWImg8188E_MAC.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/HalHWImg8188E_BB.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/HalHWImg8188E_RF.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/HalPhyRf.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/HalPhyRf_8188e.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/HalPwrSeqCmd.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/Hal8188EPwrSeq.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/Hal8188ERateAdaptive.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/hal_intf.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/hal_com.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/odm.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/odm_debug.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/odm_interface.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/odm_HWConfig.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/odm_RegConfig8188E.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/odm_RTL8188E.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_cmd.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_dm.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_hal_init.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_mp.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_phycfg.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_rf6052.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_rxdesc.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_sreset.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188e_xmit.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188eu_led.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188eu_recv.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/rtl8188eu_xmit.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/usb_halinit.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/hal/usb_ops_linux.o
  CC [M]  /home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.o
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7814:2: error: unknown field ‘private’ specified in initializer
  .private = rtw_private_handler,
  ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7814:13: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]
  .private = rtw_private_handler,
             ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7814:13: note: (near initialization for ‘rtw_handlers_def.get_wireless_stats’)
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7815:2: error: unknown field ‘private_args’ specified in initializer
  .private_args = (struct iw_priv_args *)rtw_private_args,
  ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7815:18: warning: excess elements in struct initializer
  .private_args = (struct iw_priv_args *)rtw_private_args,
                  ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7815:18: note: (near initialization for ‘rtw_handlers_def’)
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7816:2: error: unknown field ‘num_private’ specified in initializer
  .num_private = sizeof(rtw_private_handler) / sizeof(iw_handler),
  ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7816:17: warning: excess elements in struct initializer
  .num_private = sizeof(rtw_private_handler) / sizeof(iw_handler),
                 ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7816:17: note: (near initialization for ‘rtw_handlers_def’)
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7817:2: error: unknown field ‘num_private_args’ specified in initializer
  .num_private_args = sizeof(rtw_private_args) / sizeof(struct iw_priv_args),
  ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7817:22: warning: excess elements in struct initializer
  .num_private_args = sizeof(rtw_private_args) / sizeof(struct iw_priv_args),
                      ^
/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.c:7817:22: note: (near initialization for ‘rtw_handlers_def’)
scripts/Makefile.build:307: recipe for target '/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.o' failed
make[2]: *** [/home/pi/workspace/RTL8188EU/rtl8188eu/os_dep/ioctl_linux.o] Error 1
Makefile:1370: recipe for target '_module_/home/pi/workspace/RTL8188EU/rtl8188eu' failed
make[1]: *** [_module_/home/pi/workspace/RTL8188EU/rtl8188eu] Error 2
make[1]: Leaving directory '/media/mikey/BPI-USER/github/build/release/BPI-M3-bsp/linux-sunxi'
Makefile:151: recipe for target 'modules' failed
make: *** [modules] Error 2
root@bpi-iot-ros-ai:~/workspace/RTL8188EU/rtl8188eu# 

Any help in finishing this compile process is greatly apprecialted!

Thanks Anatoli

Posts: 1

Participants: 1

Read full topic

@ivkocz wrote:

Hi, please tell me how to change the resolution to Banana Pi M64 - image Ubuntu Mate 16.04? I have a resolution of 1280x720, but I need 1920x1080.

Posts: 1

Participants: 1

Read full topic