hello, when will the openwrt (kernel 4.9.119) release img be published ?
↧
Banana Pi BPI-W2 play video with openwrt (kernel 4.9.119)
↧
Banana Pi BPI-W2 (RTD1296) new image : Openwrt Lede with Kernel 4.9
Banana Pi BPI-W2 (RTD1296) new image : Openwrt Lede with Kernel 4.9
video demo on youtube:
Overview
build BPI-W2 uboot & openwrt for emmc boot ,support weston-terminal,so support weston wayland and ffmpeg
Getting started
- build uboot
a. cd Bootcode/U-Boot64
./build.sh [RTD16xx_spi|RTD16xx_emmc|RTD129x_spi|RTD129x_emmc]
b. ./build.sh RTD129x_emmc
c. ls -al DVRBOOT_OUT/RTD129x_emmc/B00-RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866-nas-RTD1296_emmc.bin
- build openwrt
a. cd OpenWRT-LEDE
b. cp -a configs/129x_kernel49_nas_videoplayer.config .config
c. make oldconfig
d. make V=s -j4
e. ls -al bin/targets/realtek/rtd129x-glibc/install.img
f. ls -al bin/targets/realtek/rtd129x-glibc/rescue
emmc.uImage
rescue.emmc.dtb
rescue.root.emmc.cpio.gz_pad.img
- install uboot to emmc (boot from SD and write uboot to emmc)
a. prepare BPI-W2 ubuntu or debian SD
b. cp -a Bootcode/U-Boot64/DVRBOOT_OUT/RTD129x_emmc/B00-RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866-nas-RTD1296_emmc.bin /media/pi/BPI-BOOT
c. BPI-W2 switch SW4 set to "1" boot from sd (ubuntu or debian) and press ESC
d. fatload sd 0:1 0x01500000 B00-RTD1296_hwsetting_BOOT_4DDR4_4Gb_s1866-nas-RTD1296_emmc.bin
e. go 0x01500000
- install openwrt to emmc
a. prepare U-DISK with fat32 file system
b. cp -a OpenWRT-LEDE/bin/targets/realtek/rtd129x-glibc/install.img /media/pi/BPI-BOOT
c. cp -a OpenWRT-LEDE/bin/targets/realtek/rtd129x-glibc/rescue/* /media/pi/BPI-BOOT
d. BPI-W2 switch SW4 set to "0" boot from emmc and press ESC
e. go ru
download link:
https://drive.google.com/drive/folders/1p5tk6-8E498llDBYnabZHJtsEosUufnr
if anyone need source code and help us to development ,please PM github account to us ,we will add you in our github team.
↧
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
This is already present in cioby23s build on lexa2 repo. Check here
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
thanks @spikerguy but I want to build my own 
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
Yes you can also build your own using lexa2 branch and install luci and adblocker just like cioby did.
↧
↧
BPI-R2 EMMC demaged
After installing OS (Stretch from Frank-FW - boot from SD, root FS on 1 partition emmc /f2fs/) on emmc, and a few hours of operation, emmc was destroyed. There was a message about the wo file system, and after reboot emmc is not detected (it is not in / dev) there is only a message in dmsg:
mmc1: error -110 whilst initialising MMC card.
Something can be done?
regards
mt_werty
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
Yesterday I have applied with success @lexa2 patches to Openwrt trunk and build a test image but for now I have the git repo locally only it’s not uploaded anywhere.
↧
BPI-R1 unstable? built-in WiFi
I often read about the instability of built-in wifi in Bpi-R1, but for me (OS: last Bananian) it has been stable for over 2 years. The problem is thermal, the chip is too small and requires a large heat sink - I glued it to a copper plate with an area of about 60x70 mm (it is not rectangular due to the housing and the elements on the board - it protrudes outside the housing - I specially cut a hole)
-
without WiFi heatsink it hung after sending 0.6-0.7 GB at max speed (samba)
-
after installing the heat sink, it hangs after sending 5-5.2 GB. (Samba)
Because in normal use I do not send such data via WIFI - it only serves as an AP for several phones and 1 laptop, the 5 GB limit at max speed is imperceptible to me.
regards
mt_werty
↧
BPI-R2 EMMC demaged
Can you access it from sdcard or uboot?
What do you mean with /f2fs/,a filesystem? Why not ext4 for rootfs?
↧
↧
BPI-R2 EMMC demaged
SD is working. Message:
mmc1: error -110 whilst initialising MMC card
i get when OS working from SD (boot from SD mmcblk0p1, root FS mmcblk0p2 /f2fs/)
F2FS? Experiment. Subjectively it is faster - I did not make measurements, but on an SD card (also on R.I.P. EMMC it was so) it works noticeably faster. I didn’t care about reliability - I don’t have anything to care about in the event of a breakdown. I didn’t expect a complete EMMC failure - at most problems with FS.
PS and to tell you the truth, I think f2fs is not the cause here - it has been working for several weeks on the SD card as rootfs.
↧
Is there a list of compatible MIPI displays?
Thanks @sisyphos. This was a very informative post. So, if I understand you correctly, I need to match two things:
- Find a display which has a connector fitting the BananaPi in question. I also need to make sure the display itself has a resolution the BPi supports.
- I need to find the drivers for its MIPI bridge, whichever that is.
Is that about right?
↧
Builtin wifi not detected
Nope. Installed debian buster image and it works with it.
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
Nice job, congrats! Wanted to mention that it makes me slightly uncomfortable when people mention “lexa2 patches”. I want to clarify that those are in fact a collective effort - as it typical for OSS world. I’ve done my small bit of job arranging things like building u-boot package for R2 or creating script to produce SD images. Other than that the only thing I’ve done was to rearrange other people work and provide configuration/scripts to make it all come together. Let’s call it “lexa2 fork” or “patches from lexa2 fork” - this way I don’t get credit for the things I didn’t do.
↧
↧
BPI-R2 EMMC demaged
F2FS is a good filesystem to use on flash storage. And I don’t think your eMMC problems are caused/related to F2FS. It’s more probable that you just been hit by Murphy’s law - your eMMC failed because everything fails from time to time. Still it’d be good idea to show us your kernel messages log (dmesg), at least parts related to mmc* - there might be some more messages hiding there you missed out, who knows? Nevertheless if it’s really the case of failed eMMC chip - it is possible to fix by replacing chip. Look for component level repair shops near your location (i.e. guys who repair motherboards, videocards or mobile phones) and ask them for help. It is like a 15 minutes task for experienced person to replace eMMC chip using bottom heater + hot air soldering gun and eMMC chips are dirt cheap if we’re talking about small storage capacities like 8 or 16GBs.
↧
BPI-R2 EMMC demaged
I think so too. but I paste:
# dmesg|grep mmc
> [ 0.000000] Kernel command line: board=bpi-r2 console=earlyprintk console=tty1 fbcon=map:0 console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=f2fs rootwait vmalloc=496M debug=7 initcall_debug=0 video=1280x1024
>
> [ 5.013733] mtk-msdc 11240000.mmc: GPIO lookup for consumer cd
>
> [ 5.019545] mtk-msdc 11240000.mmc: using device tree for GPIO lookup
>
> [ 5.025934] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/mmc@11240000[0]' - status (0)
> [ 5.035412] mtk-msdc 11240000.mmc: Got CD GPIO
>
> [ 5.039832] mtk-msdc 11240000.mmc: GPIO lookup for consumer wp
>
> [ 5.045659] mtk-msdc 11240000.mmc: using device tree for GPIO lookup
>
> [ 5.051994] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@11240000[0]'
>
> [ 5.060724] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@11240000[0]'
>
> [ 5.069381] mtk-msdc 11240000.mmc: using lookup tables for GPIO lookup
>
> [ 5.075880] mtk-msdc 11240000.mmc: lookup for GPIO wp failed
>
> [ 5.142558] mtk-msdc 11230000.mmc: GPIO lookup for consumer wp
>
> [ 5.148374] mtk-msdc 11230000.mmc: using device tree for GPIO lookup
>
> [ 5.154757] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@11230000[0]'
>
> [ 5.163508] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@11230000[0]'
>
> [ 5.172166] mtk-msdc 11230000.mmc: using lookup tables for GPIO lookup
>
>
> [ 5.178651] mtk-msdc 11230000.mmc: lookup for GPIO wp failed
>
> [ 5.228806] mmc0: host does not support reading read-only switch, assuming write-enable
>
> [ 5.239126] mmc0: new high speed SDHC card at address 0007
>
> [ 5.291156] mmcblk0: mmc0:0007 SD32G 29.0 GiB
>
> [ 5.297160] mmcblk0: p1 p2
>
> [ 8.357693] F2FS-fs (mmcblk0p2): orphan cleanup on readonly fs
>
> [ 8.383593] F2FS-fs (mmcblk0p2): Mounted with checkpoint version = 1178
>
> [ 8.831677] mmc1: error -110 whilst initialising MMC card
>
> [ 12.071539] mmc1: error -110 whilst initialising MMC card
>
> [ 13.245596] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt.
> Please run fsck.
>
> [ 15.331807] mmc1: error -110 whilst initialising MMC card
>
> [ 18.501538] mmc1: error -110 whilst initialising MMC card
it’s after systems crash
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
@LeXa2 How do I flash an image built from your 18.06 fork onto EMMC? the only generated ext4 images are sdcard and sysupgrade.
↧
BPI-R2 new image: OpenWrt 18.06.2 source code fork
For eMMC you will have to do some manual work: install preloader to boot0 eMMC hardware partition and then upload generated SD card image to the board and dd it to the main hardware partition of eMMC. IIRC that’s enough to make it fly, i.e. shutdown your board then, remove SD card, power it back on. Due to the way board works there’s a small chance it will stuck failing to find preloader, press “reset” button in this case while continuing to keep power button pressed.
A fair warning: I’m writing this from the top of my head being like 300km away from my testing R2 board right now. Give above suggestions a try and report back your results, we will help you to figure things out from there on.
↧
↧
Is there a list of compatible MIPI displays?
Well, there are some limitating factors from the board itself like that a resolution of 1024x768 in 256 colors already takes about 800k, and 1920x1080 takes about 2GB of memory and the board itself only has 2GB (unless we talk about static images). Additional higher resolution panels need usually more data lanes to transfer this amount of image data and the Bpi-M64 has max 4. Last but not least painting this data with a certain refresh rate ask for a very high operation frequency to process and deliver the data. So while there are reports of people to output 4k via HDMI on raspberry pi, they usually then had a refresh rate of only 15Hz.
Apart from that the board itself isn’t necessarily the limiting factor but the software and drivers are.
If you are able to run one of the more recent OS like it is available from Android or Armbian, then you have a good chance this version already support more display drivers and higher resolutions out of the box. Also the Armbian community may be able to help you more on the software side to get a particular screen up and running.
Sadly for me, my board doesn’t like this latest Armbian and crashes with kernel panic, but it might be related to my particular board revision. So I currently attempt to recompile the Debian 9.5 image and hopefully will be able to add some of the currently disabled drivers and modules. But this is an entirely different topic.
That isn’t meant to discourage you but to say that there is no one trick poney answer as it might depend on your willingness to tinker with software and board and which is why I asked for the OS you are or intend to use.
I would suggest, try if you can get Armbian running then you should already be able to load some driver modules at runtime without needing a recompile.
↧
BPI-R2 EMMC demaged
Thanks for sharing. Error -110 is ETIMEDOUT thus I’m afraid it’s probably eMMC chip died on you. Or it might be some other hardware problem like cracked solder joint, e.t.c. Replacing eMMC chip with a new one is your best bet for this case.
↧
BPI-R2 EMMC demaged
Thank you very much for help. 
↧