__Dirk__

Members
  • Content Count

    16
  • Joined

  • Last visited

1 Follower

About __Dirk__

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I cannot push anything for the H64 board device tree as the H64 model-B uses the model-A dts with some modifications. I asked for a model-B specific device file but got no answer. April 7 @martinayotte Can the Pine64 H64 model-b get it's own device tree in the repo ? At the moment it includes the model-a and does some small changes on the model-a device tree. Regards, __Dirk__
  2. Hi, Since I still couldn't find a enclosure for my Pine64 H64 model-B, I mocked up one myself using a Eur 6,50 Raspberry Pi 4 case. 1) From the USB/ETH connector side I cut out the sections in between the connectors since there is a small offset that pushes the Pine64 board aside when closing the case. 2) From one of the cover lulls, I cut out a section to fit over the IR sensor. 3) On the HDMI side I cut out the two ports holes of the RPI micro hdmi connections and I made a notch in the USB-C hole to fit the power connector of the Pine64. 4) Drilled a hole in the cover large enough for the WIFI/BT antenna connector, on the board, to fit through. The pcb takes the exact same mounting points inside the enclosure as the rpi4, so you don't have to fiddle around there. MicroSD card slot matches exactly I only forgot to add some holes for the two buttons (Reset/Poweroff) on the SDcard side. A very thin hot knife works very nice to cut in/out the case material. Regards, __Dirk__
  3. Nice... streaming music (using VLC mediaplayer) from my NAS to a Bluetooth 5.0 amplifier works as well
  4. @martinayotte Can the Pine64 H64 model-b get it's own device tree in the repo ? At the moment it includes the model-a and does some small changes on the model-a device tree. Regards, __Dirk__
  5. All, Don´t know if anybody else did it... but I got Bluetooth running by modifying the device tree and adding support for communication between the RTL8723BS and UART1 and loading the needed RTL8723B firmware. Distro: Armbian Buster Kernel version: 5.4.30-sunxi64 This is how I did it: 1) Create a patch (xx.patch) with the next content and place it in ~/build/userpatches/kernel/sunxi-current/ --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-04-06 12:37:45.584912094 +0200 +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-04-06 12:37:45.584912094 +0200 @@ -498,6 +498,21 @@ status = "okay"; }; +/* On Wifi/BT connector, with RTS/CTS */ +&uart1 { + pinctrl-names = "default"; + pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; + status = "okay"; + + bluetooth { + compatible = "realtek,rtl8723bs-bt"; + device-wake-gpios = <&r_pio 1 1 GPIO_ACTIVE_HIGH>; /* PM1 */ + host-wake-gpios = <&r_pio 1 2 GPIO_ACTIVE_HIGH>; /* PM2 */ + reset-gpios = <&r_pio 1 4 GPIO_ACTIVE_LOW>; /* PM4 */ + post-power-on-delay-ms = <200>; + }; +}; + &usb2otg { dr_mode = "host"; status = "okay"; 2) Run sudo ./compile with your favorite config (Desktop/server/blablabla) 3) Flash the image to an SD card or eMMC module. 4) Start your Pine64 H64 model-B 4) Connect to a network and run the firmware update/upgrades (armbian-config) and install the Bluetooth tools. 5) DO NOT ENABLE SERIAL 1 !!!! in armbian-config 6) Download the next git repo to your board: https://github.com/lwfinger/rtl8723bs_bt.git 7) Unpack the archive, run make 8) Copy the next firmware files to /lib/firmwares/rtl_bt: sudo cp rtlbt_fw_new /lib/firmware/rtl_bt/rtl8723bs_fw.bin sudo cp rtlbt_config /lib/firmware/rtl_bt/rtl8723bs_config.bin 9) Reboot Expected dmesg output: [ 45.107273] Bluetooth: HCI UART driver ver 2.3 [ 45.107279] Bluetooth: HCI UART protocol H4 registered [ 45.107281] Bluetooth: HCI UART protocol BCSP registered [ 45.107329] Bluetooth: HCI UART protocol LL registered [ 45.107331] Bluetooth: HCI UART protocol ATH3K registered [ 45.107375] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 45.107509] Bluetooth: HCI UART protocol Intel registered [ 45.107592] Bluetooth: HCI UART protocol Broadcom registered [ 45.107614] Bluetooth: HCI UART protocol QCA registered [ 45.107616] Bluetooth: HCI UART protocol AG6XX registered [ 45.107642] Bluetooth: HCI UART protocol Marvell registered [ 45.845446] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000b lmp_ver=06 lmp_subver=8723 [ 45.849521] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 45.849529] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723bs_fw.bin [ 46.055000] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723bs_config.bin [ 46.096579] Bluetooth: hci0: RTL: cfg_sz 55, total sz 23699 [ 46.929071] Bluetooth: hci0: RTL: fw version 0x373e6962 'hciconfig list' output: hci0: Type: Primary Bus: UART BD Address: 48:46:C1:3A:6B:5F ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:1982677 acl:3028 sco:0 events:491 errors:0 TX bytes:91688 acl:232 sco:0 commands:225 errors:0 File transfer from Pine to Samsung is working... haven't tested anything else.. Regards, __Dirk__
  6. Dear all, Finally managed to get my Pine64 H64 model-B to boot from the Foresee 32GB eMMC module after applying the next patch that adds HS200 and HS400 support to the device tree. --- a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-03-30 11:24:41.176470382 +0200 +++ b/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts 2020-03-30 11:24:41.176470382 +0200 @@ -127,8 +127,10 @@ pinctrl-0 = <&mmc2_pins>; vmmc-supply = <&reg_vcc3v3>; vqmmc-supply = <&reg_vcc1v8>; - non-removable; cap-mmc-hw-reset; + mmc-hs200-1_8v; + mmc-hs400-1_8v; + mmc-hs400-enhanced-strobe; status = "okay"; }; Don know how this patch will impact other brand/type eMMC modules... but for me this now works!!!!! @martinayotte, I guess your remark pushed me in the correct way :-D Regards, __Dirk__
  7. Igor, Thank you for your reply. I did not mean to insult anybody by stating 'Armbian dev's do not seem to care for the few boards that do not work out of the box either.' but it's a fact and an understandable one as you already noted .. budget, time , etc.. Another fact is that there seems to be a bug in the Armbian build for certain eMMC modules... the hardware (Pine64 H64-B and eMMC I have) are verified to be working... it's running on AOSC without any problems. I am happy to put time in investigating why.. (although my knowledge about SBC's in not by far as extended as your's)... From the thread all I got from my questions is.. it works for me ... that is not helpful .. and I understand that if you don't have the board you can't test anything.. even if you DO have the board.. if you can't reproduce the problem, it's difficult to help. But you do have the knowledge to give me a hint on where to start, it's somewhere in the booting process.. so is it u-boot not setting up the environment correctly, or is it the kernel , or the board config files? ... or.. .? I think I posted all the logs (Console output, dmesg) to give me some hint on where to start looking... older kernel, older u-boot ... kernel patch .. any other hints.. That's what I was looking for.. a hint to continue.. not asking anybody to solve my problem.. To end this reply... A big thank you for developing Armbian and sharing it with the community! Kind regards, __Dirk__
  8. JK, Thanks for sharing your findings! :-) I was looking into compiling Armbian with an older version of u-boot (same as the AOSC) but the extended compile options for armbian do not support this... as far as I can see.. Armbian dev's do not seem to care for the few boards that do not work out of the box either. So for now I chucked the Pine aside and switched to a Raspberry 4.. just costs me to much time to get all things I want running on the H64 B Regards, __Dirk__
  9. Update: Out of curiosity I downloaded the "AOSC Community Build Image with Mate Desktop [eMMC Boot] [20180216]" for my Pine64 H64 and wrote the image to the eMMC module using Balena etcher... It's running.. without any issues...... __Dirk__
  10. Gents, Giving it a 2nd, 3rd, 4th .... try... dmesg show trouble with reading the eMMC module (mmcblk2) on startup. When the system is booted there is no trace of the mmcblk2 block device and running "fdisk -l " just never returns.. whereas it does when the eMMC is not installed. Edit: The dmesg output is from the EMMC module installed and formatted as ext4 without any further content. SBC booting from SD. The eMMC does work from the USB2eMMC converter... so the question is.. is the board broken or incompatible with the eMMC module ? I can ask the seller for support.. but I am not expecting to much from them.. @NicoD , Would it be an option to send my board and eMMC module to you so you can filter out the culprit with your "know to be working" hardware ? [ 3.320856] libphy: stmmac: probed [ 3.476407] mmc2: new DDR MMC card at address 0001 [ 3.477631] mmcblk2: mmc2:0001 NCard 28.9 GiB [ 3.478413] mmcblk2boot0: mmc2:0001 NCard partition 1 4.00 MiB [ 3.479158] mmcblk2boot1: mmc2:0001 NCard partition 2 4.00 MiB [ 3.480389] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.480690] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.480957] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.481223] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.481488] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.509232] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 3.596826] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.596887] blk_update_request: I/O error, dev mmcblk2, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 3.596897] Buffer I/O error on dev mmcblk2, logical block 0, async page read [ 3.597218] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.597491] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.597758] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598024] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598291] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598559] sunxi-mmc 4022000.mmc: data error, sending stop command [ 3.598598] blk_update_request: I/O error, dev mmcblk2, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [ 3.598604] Buffer I/O error on dev mmcblk2, logical block 0, async page read [ 3.598623] mmcblk2: unable to read partition table Regards and thank you in advance, __dirk__ Netherlands
  11. Btw.. the ext4 or FAT32 formatted eMMC should show up in /dev/disk/by-uuid ..when the board fully booted from SD card... right? Dirk
  12. Martin, I gave your image a try on the eMMC module.. unfortunately.. same behavior.. it hangs after: Begin: Running /script/local-block .. done.. I guess I have to go to the reseller and verify the working of either the eMMC module or the board.. :-( Thanks for your effort though! Regards and happy holidays! Dirk
  13. Martin, Sounds like an idea. I'll give it a try.. thnx! :-D Btw.. probably not related.. but on the site of Pine64.. there is no 32GB related eMMC product.. only the 16GB and 64GB...coincidence? Since I have the 32GB.. https://store.pine64.org/?product=pine-h64-model-b-3gb-single-board-computer Regards, Dirk
  14. Gents, Thank you for your reply. I have a pine_H64_MODEL_B revision board. Production date? 2018-12-12