@spikerguy: Thanks, yes this seems to be right. Thanks a lot!
↧
Which version of Banana Pi do I have?
↧
Banana Pi m1 Plus case design files
Hi dear all I have designed final case for Banana Pi M1+. The files are attached. detal1_1x.dxf (204.5 KB) detal2_1x.dxf (205.6 KB) detal3_1_3x.dxf (204.3 KB) detal3_2_3x.dxf (202.8 KB) detal3_3_3x.dxf (203.1 KB) detal4_3x.dxf (204.9 KB) detal5_1x.dxf (204.9 KB) top_bottom.dxf (210.2 KB)
2019-11-02T20:00:00Z
↧
↧
BPI-R64 current u-boot support
Emmc seems to work only if pre-initialized (e.g. by previous loaded uboot or by booting from emmc). if booting directly from sd it does not work.
If anybody has an idea…
↧
How to use BPI-4G LTE module with BPI-R2
↧
BPI-M4 android Getting started
- Burn image to emmc, and switch SW2 on the side of SD card to “1” position, which starts from emmc
- Our M4 does not include nandflash circuit design, only emmc and SD
- BOOT_SEL is fixed when RTK leaves the factory and cannot be modified
- Functions of SW2 and SW5 are easy to understand from the schematic diagram
- SW4 is for system upgrade
↧
↧
Banana Pi product CE,Fcc,RoHS certification wiki page
All banana Pi product CE,Fcc,RoHS certification,we have update to wiki page:
↧
BPI-M3 cldnn / openCL
Dear,
I cannot find how to install opencl driver for BPI-M3 or how to download cldnn for PowerVR GPU. Please help me!
↧
BPI-R64 current u-boot support
Now, we’re also developing mt7622 upstream uboot, and will share our patches with you in these two days.
-
Ethernet: todo
-
PCIe/USB: ongoing
We’ll use mt7629 as target platform first because it has uboot usptream already with similar IP.
↧
Which preloader image to use?
@sinovoip have you changed preloaders (at least for emmc)?
I guess sd-preloader cannot be changed if it is also loaded on emmc (like on r64) and will override emmc-string.
↧
↧
Which preloader image to use?
↧
Which preloader image to use?
As this differs from eMMC string,how can we now check for bootsevice in uboot? Which address is set to which byte (i guess 0xea).this should work too if sd is available but boot from emmc
it looks like you read boot signature from first bytes (SDMMC_BOOT vs. EMMC_BOOT) of mmc-device…but how is this passed to uboot?
↧
How to use BPI-4G LTE module with BPI-R2
I know that page, however none of my questions is being answered there.
↧
Which preloader image to use?
The uboot code doesn’t need to change, just like before
↧
↧
Which preloader image to use?
We should have EMMC string on memory address 0x81dffff0?
↧
Which preloader image to use?
yes, R2 have update this code.
↧
Which preloader image to use?
Thank you, we will try this one: https://github.com/BPI-SINOVOIP/BPI-files/blob/master/SD/100MB/BPI-R2-EMMC-boot0-DDR1600-20191024-0k.img.gz
@LeXa2 can you try it too?
edit:
echo 0 > /sys/block/mmcblk1boot0/force_ro
gunzip -c BPI-R2-EMMC-boot0-DDR1600-20191024-0k.img.gz | dd of=/dev/mmcblk1boot0 bs=1024 seek=0
seems to work well:
BPI-R2> md.b 0x81dffff0 4
81dffff0: 65 4d 4d 43 eMMC
i can also load bigger uboot (2020-01 with ahci-support, so it looks good so far)
↧
BPI-R64 current u-boot support
have you emmc-access ready? Is it also working if booting from sdcard?
Can you share this patch (maybe pinctrl/timer)?
↧
↧
BPI-R64 current u-boot support
@moore can you please give us difference on things preloader initialized to boot form eMMC and from SD.
Because we have it worked when first uboot started from eMMC and not worked when from SD.
Boot src eMMC status SD status
eMMC works works
SD no works
So for case it boot from SD something (clk, pinctrl, power, etc) did not initialized, so eMMC won’t work. But we can’t catch yet, what is it.
Thanks.
↧
BPI-R64 current u-boot support
@frank-w did you try to boot linux from SD (both uboot and linux from SD) and check if eMMC accessible?
↧
BPI-R64 current u-boot support
have not get managed it…copied kernel+dtb (which i load from my older uboot) to root of sd-card and did this:
U-Boot MT7622> setenv bootargs console=ttyS0,115200 root=/dev/mmcblk1p2 rw rootwait
U-Boot MT7622> ls mmc 1:1
bananapi/
0 sd.txt
8841288 uImage_5.4
23721 bpi-r64-5.4.dtb
3 file(s), 1 dir(s)
U-Boot MT7622> setenv kaddr 0x44000000
U-Boot MT7622> setenv dtaddr 0x47000000
U-Boot MT7622> fatload mmc 1:1 $kaddr uImage_5.4
8841288 bytes read in 785 ms (10.7 MiB/s)
U-Boot MT7622> fatload mmc 1:1 $dtaddr bpi-r64-5.4.dtb
23721 bytes read in 8 ms (2.8 MiB/s)
U-Boot MT7622> bootm $kaddr - $dtaddr
## Booting kernel from Legacy Image at 44000000 ...
Image Name: Linux Kernel 5.4.0-rc1-r64
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 8841224 Bytes = 8.4 MiB
Load Address: 40080000
Entry Point: 40080000
Verifying Checksum ... OK
## Flattened Device Tree blob at 47000000
Booting using the fdt blob at 0x47000000
Loading Kernel Image
Loading Device Tree to 7bff7000, end 7bfffca8 ... OK
Starting kernel ...
then it hangs till a board-reset occours
did same steps with my old uboot (where i have additional env-vars set) and i see kernel booting…with this running i see emmc-partitions and can access them
root@bpi-r64:~# hd /dev/mmcblk0boot0 | head -1
00000000 45 4d 4d 43 5f 42 4f 4f 54 00 00 00 01 00 00 00 |EMMC_BOOT.......|
root@bpi-r64:~#↧