Recent Profile Visitors

Ok thanks for the info.
Was just wondering, because on the mikroBus Header there's also a 5V out.
But in the meantime I also measured the voltage on the tx pin of the clearfog and that's at max 3.3V due to pullup resistors.
So 3.3V seems like a safe choice.
Greetings!

Yes I am sure that the I2S0 port is enabled, Armbian provides a overlay for that (https://github.com/armbian/build/blob/18215550b367919c1b270185e110b901e2843edd/patch/kernel/sunxi-next/add-sunxi-overlays.patch#L2246-L2276)
Which I enabled via Armbian-Config / armbianEnv.txt... Also checked that the device is there using /proc/device-tree/
That is also the reason why I didn't keep the I2S -> Okay Lines from the Raspberry PI overlay.
That the driver is normally not included is correct, I will add it and then build my own image. But first I would love to get the device tree overlay working.
I will conduct some more testing this afternoon or tomorrow and update this reply with my results.
EDIT:
So I've got the nodes integrated in the device tree, but not using overlays but decompiling and recompiling it online with dtc.
I added the following nodes, maybe someone can create a overlay from that?
// under soc
sound:sound {
compatible="hifiberry,hifiberry-dac";
i2s-controller=<0x99>; // this is taken from above i2s controller, in the overlay there should be a label I guess
status="okay";
};
// in the root
pcm5102a-codec {
#sound-dai-cells = <0>;
compatible = "ti,pcm5102a";
status="okay";
};
Testing in /proc revealed the changes had been loaded correctly.
Then I tried compiling my own kernel with the PCM5102A driver but the option is not displayed in the kernel configuration.
Any ideas?
Greetings,
count-doku

Hi,
I have the Banana Pi M1 and the Banana Pro and just received a I2S to Analogue Module.
I'd love to use these together but unfortunately there is no device tree overlay available.
The module is from Adafruit (https://learn.adafruit.com/adafruit-i2s-stereo-decoder-uda1334a) they also mention it is the same chip / driver that is also used by the Hifiberry DAC,
there is support for Raspbian also with an overlay etc. (see the Raspberry PI kernel tree | https://github.com/raspberrypi/linux/blob/rpi-4.14.y/arch/arm/boot/dts/overlays/hifiberry-dac-overlay.dts).
I tried adapting the overlay for usage with the Banana but didn't get it running.
So any help would be greatly appreciated, I will then of course test and report. Also have a uart to usb cable to access uboot and can build images.
This is what I have so far:
/dts-v1/;
/plugin/;
/ {
compatible = "allwinner,sun7i-a20";
fragment@0 {
target-path = "/";
__overlay__ {
pcm5102a-codec {
#sound-dai-cells = <0>;
compatible = "ti,pcm5102a";
status = "okay";
};
};
};
fragment@1 {
target = "/soc@01c00000";
__overlay__ {
sound: sound {
compatible = "hifiberry,hifiberry-dac";
i2s-controller = <&i2s0>;
status = "okay";
};
};
};
};
Of course using above overlay and enabled I2S0 Port already with Armbian-Config / armbianEnv.txt and the provided overlay.
Naturally there is a driver / codec required to get the Sound Module working, but I think we could use the driver from the Raspbian Kernel Source:
https://github.com/raspberrypi/linux/blob/rpi-4.14.y/sound/soc/codecs/pcm5102a.c
Doesn't seem to rely on anything raspberry specific.
I would integrate, test and the do a PR on github, with this stuff, but need some help getting the overlay working first.
Greetings,
Count-Doku

Hi,
I updated my ClearfogPro today and noticed (that like in the last updates), updating the linux-u-boot-clearfogpro-next package fails,
with the error "/dev/mmcblk2" doesn't exist".
This happen obviously, because I don't have a SD Card installed, as I am using a M.2 SSD to boot and as root.
Quick check inside the .deb file revealed the platform_install.sh which only tries writing the u-boot.mmc version to /dev/mmcblk2.
For me this is not a big problem, I know how to get the correct u-boot into place (/usr/lib/linux-u-boot-next-clearfogpro_5.60_armhf/u-boot.sata) but new users might find it difficult.
Would it be possible to let the users select the device for writing the u-boot when the mmc variant fails?
Just a popup with a text saying: "Could not write u-boot to default location (sdcard/mmc), please specify device" and a textbox below...
(Might even look into doing something like this myself and then send a PR)
Or does Armbian normally keep track of where the u-boot is and I just did something wrong when moving from sdcard to ssd?
Greetings,
count-doku
EDIT:
Just realised this might apply to other boards to, if it would better fit into Development or so, please move.

Yes you could use the Pins from the mikrobus header but make sure your fan does not draw to much power for the 5V regulator.
If it is a 12V fan you could also run it directly on your input (if this is 12V). There are some headers near the power plug which can be used with a small adapter.
I attached an image which highlights the connectors.
Check https://wiki.solid-run.com/lib/exe/fetch.php?media=a38x:carrierboard:docs:clearfog-schematics-2.1.pdf for the schematics.
The power regulators etc are on page 13...
EDIT: looks like the power regulator for 5V is the RT2875A/B which can source up to 3A.
Greetings

Answer to question 1:
Yes eth0 goes to the isp box. And br0 to my network. But I forward my global ipv4 from the isp box directly so they are not the same network.
Internet ---- ISP Box (Modem) ------ Clearfog -------- br0 ------ lan1-6
77.11.22.33 192.168.1.1 \-- wlan
So the clearfog is directly connected with the internet and the isp box is a completely transparent ethernet / dsl bridge.
---
Answer to second question:
yes they are configured manually. The auto stanza only means the interfaces get ifup'ed automatically.
The actual lan ports (1-6) don't get IPs themselves. They only got MAC Addresses (like a switch). Only the br0 interfaces has a local ip (192.168.1.1).
Then all packets from lan1-6 go over the br0 interface. All the routing etc. is based on that.
Greetings

There is a perfect guide for installing to M.2 SSD available here: https://github.com/nightseas/arm_applications/blob/master/doc/getting_started_with_clearfog_base.md
Bottom page comes the M.2 SSD part.
If you want to make use of your existing setup on the sd card, just use another device (eg. computer) to make an img of the sd and then write it to the m2. Just remember flashing the new uboot to the m2 disk.
But thats also described in above article. I recently used it to port everything from sd to m.2 ssd and it works like a charm. The sd card ain't even neccessary to boot.