hitech95

I tied with this: https://pastebin.com/hXy19ujx but without lucky. I'm tring to control that clk gate that but is managed by the kernel. But today randomly that memory set worked and i got the clock out. But i'm still having the timeout problem with BT.

Why years? The driver to hook into hci should already be in mainline (the same used by RPI)

On Sunxi IRC they told me that that clock gate is handled by the kernel. So a module is needed. They told me to watch linux serdev and associated stuff. Any idea? Does someone tried this?

According to the datasheet of R16/A33 it should be the same address but I can't get the clock output working. (See page 136 and 143 of R16 User manual ) root@bananapim2m:~# devmem2 0x1f00060 b 1 /dev/mem opened. Memory mapped at address 0xb6fd8000. Illegal data type '▒'. root@bananapim2m:~# At this point i have no idea on how i could test this out... if someone have a brilliant idea It maybe that I'm missing this (so the clock is not set properly)? rfkill-gpio

Uhm... this is not new to me. I'm working on my own SBC and i have seen lot's of errors. Now I check on A33 Datasheet to see if that register is present. Another question how did you get that base address? 0x60 is the register but that 0x1f00000? Yup, my typo. I have found that page on the wiki. No idea why I don't have seen that before! (sorry for the time loss)

But according to the datasheet this disable something not enabling (if I git it right that command write a 0x01 as a byte to that register). Another question: how is mapped the gpio export with the ports? (Does you have a reference to check) for example on dts <1 10> is PORTA 10 but on export I have no idea on how the count is done. Is it divided by bank? I have seen that my SoC have gpiochip0 and gpiochip352.

Ok so I just need to set the reset pin low and start with the hciattach. I have seen that this BT module receive the 32KHz clock from the clock output pin. (X32KFOUT) but i'm not sure if this clock is always present on R16/A33. right now I don't have a scope to test it out. I have seen that someone use the rfkill gpio module to do that!

So the reset is not handled by the driver? So i just need to disable the resets? What is this line? devmem2 0x1f00060 b 1

Ok now it boot up each time. I tried to install on MMC and it works fine. For now only BT seems that it is not working. on hciattach i get a timeout. Not sure why, maybe i need to add something to the DTs to enable it? I have seen that BT have a lot of reset/enable/wake lines but I don't see where I can map those.

Thanks I'll try. According to the schematic the UART is 0 so tty0 should be right.

Hi guys I'm working to port the bpi-m2m to armbian. Right now i'm having a strange behaviour. I'm new to armbian development. I only use it for a npi-neo back in time. Anyway, my problem is quite simple. I have a working uboot and a working kernel (I think). the decive tree is in mainline. Looking the schematic, the DTS looks it is ok. I crated the armbian configuration, buit an image and it started "working" (you will se why is inside teh quote mark later) . Somehow i got a shell via UART. I configured the wireless AP and I got a working image. (Only BT was not working, no idea why). Due to the BT problem I decided to reboot the SBC and the problem I got before showed up again, but this time worse then before. After the kernel boot (which i'm not able to see, how can enable the serial output during kernel boot?) the init/systemd start loading all the deamons and after a while instead of having a console i got nothing. Then after a fiew seconds AXP PMIC shutdown the board (for no reasons, i don't have the kernel log to see what is going on). I would like to know if someone had this type of problem. If I use another rootfs (same uboot and same kernel) like one made on yocto all works fine. My mayor questions is, how can i enable the serial logging? This device doesn't have a display, it couldd be headless and it don't have a ethernet connection so i can access it only by serial. For reference this is my bootlog: https://pastebin.com/0gEr8jcGIf I change the bootarg and I add the "init" parameter to the kernel and I specify the path for the shell I get a working image: https://pastebin.com/qFDQ4JGW Regards, Nicolò

Hi guys, I'm new to the forum, I just received the NanoPi Neo 2, small, pretty. I downloaded the compilation tools and I created a debian jessie image, configured and installed all the needed packages. Than I've noticed something strange: the energy consumption is much higher again to the standard ubuntu firmware 2x. I tried to investigate but after fiew minutes i stopped. Than I'm going to configure the led: with my surprise the LEDs are named as orangepi:red:status ... I do a check on the DTs and find out that the wrong DTS has loaded. root@nanopineo2:~# cat /sys/class/leds/orangepi\: orangepi:green:pwr/ orangepi:red:status/ root@nanopineo2:~# cat /sys/class/leds/orangepi\:red\:status/ brightness max_brightness subsystem/ uevent device/ power/ trigger root@nanopineo2:~# cat /sys/class/leds/orangepi\:red\:status/trigger [none] kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport usb-gadget usb-host mmc0 heartbeat cpu0 cpu1 cpu2 cpu3 rc-feedback 1c30000.ethernet-0:00:1Gbps 1c30000.ethernet-0:00:100Mbps 1c30000.ethernet-0:00:10Mbps rfkill-any root@nanopineo2:~# echo heartbeat > /sys/class/leds/orangepi\:red\:status/trigge root@nanopineo2:~# cat /proc/device-tree/ #address-cells gmac-3v3/ psci/ thermal-zones/ aliases/ interrupt-parent r-gpio-keys/ timer/ chosen/ leds/ serial-number usb0-vbus/ clocks/ memory/ #size-cells vcc3v3/ compatible model soc/ cpus/ name __symbols__/ root@nanopineo2:~# cat /proc/device-tree/model Xunlong Orange Pi PC 2 root@nanopineo2:~# cat /proc/device-tree/compatible xunlong,orangepi-pc2allwinner,sun50i-h5r root@nanopineo2:~# Suggestions? EDIT: Looks like that also the U-Boot is for the orange PI, not sure how the kernel / bootloader works on all winner so it maybe the bootloader that has the problem? INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON U-Boot SPL 2017.01-rc1-g5df570f-dirty (May 09 2017 - 10:42:28) DRAM: 512 MiB Failed to set core voltage! Can't set CPU frequency Trying to boot from MMC1NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 10:42:22, May 9 2017 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2017.01-rc1-g5df570f-dirty (May 09 2017 - 10:42:37 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: OrangePi PC 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 720x576i composite-pal console (overscan 32x20) Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga Net: phy interface7 Could not get PHY for ethernet@1c30000: addr 1 No ethernet found. Hit any key to stop autoboot: 0 38518 bytes read in 132 ms (284.2 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2428 bytes read in 208 ms (10.7 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 116 bytes read in 169 ms (0 Bytes/s) 19253 bytes read in 325 ms (57.6 KiB/s) 4904371 bytes read in 531 ms (8.8 MiB/s) 11270152 bytes read in 743 ms (14.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4904307 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 reserving fdt memory region: addr=4fa00000 size=5000 Loading Ramdisk to 49b52000, end 49fff573 ... OK Loading Device Tree to 0000000049b4a000, end 0000000049b51fff ... OK Cannot setup simplefb: node not found Starting kernel ... Loading, please wait...