Banana Pi BPI-P2 Pro is an ultra compact single board computer measures only 65mm*52.5mm. It uses 64bits quad-core Arm Cortex-A35 Rockchip RK3308 processor, with 2G RAM memory.8G eMMC flash,100M LAN,add PoE function support ,Wifi & Bluetooth onboard, It’s ideal for light-weight systems with some space-limited applications. Like other members of Banana Pi,
Ps. I don’t trust your LAN cable, where the rubber shell isn’t part of the plastic connector.
The individual pin connections can get loose quite easily now.
1.We don’t have an officially supported armbian image yet. Regarding the account and password you mentioned, this is the same as other armbian systems. You will be asked to enter your account and password when you start it for the first time. The default is root/1234.
2. Powered by typec
Is there an better document on how to burn an image to a SD Card. I assume you have to marry the two images to make a bootable image
Image Files
p2pro-debian11.img
armsom-p2pro-buildroot.img
Because using Etcher you get an error with both images. No offence Arm SoM Wiki is bad, very hard to follow. I am trying to get my unit so that I can do a video on it.
Using PoE I do not get access to usb devices. Neither usb-a nor usb-c. The board does not list up any connected usb flash device via fdisk. If I use usb-c to power up usb-a works as normal. But in this situation I would never be able to use a usb-c flash device. Has someone else also experienced this? Currently we have to stay with the p2 zero board furthermore. Any help would be appreciated.
How can I create a backup of the SD card as a .img file? Win32Disk Imager doesn’t recognize the SD card, and using the ‘dd=’ command, the .img file can’t be written using Rockchip SD Disk Tool
After playing around with my newly delivered P2-PRO (using Windows RKDevTool 2.84 and armsom-p2pro-debian-bullseye-base-arm64-20240524.img went well), I tried to flash some other linux rk3308 image with linux rkdeveloptool.
Seems I bricked it as it doesn’t register on USB when I do the maskrom procedure.
LEDs are constant red and blue, green is flash-flash-0.2s pause.
Unfortunately, I haven’t found any description yet, what the blink code means and how to re-enable the SBC again
FYI: I succesfully recovered the P2Pro by booting from SDCard. Just installed the debian image on an SD[1] and booted. I was able to re-install on emmc, also
Aha. Well, they are making their own builds too, containing stock Rockchip / Allwinner kernel. Most of our builds, our primary focus, goes into mainline based kernels … And in this particular SoC, it is possible that mainline support is already better, but this will need to be confirmed by one of the developers that is dealing with this SoC.
From maintaning perspective, it would be best if they contribute to our build framework, and make images from there. Its less confusiong. We will try to provide assistance from our side to make this easier. Having another custom kernel in our framework is not a problem. There are several vendors using this option.
The individual pin connections can get loose quite easily now.
