Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI
I tried :
hciattach -n ttymxc2 texas
... but got "Initialization timed out."
I also tried various combinations of bit rates and flow control.
Any tips are welcome.
for a while now i have been struggling to create a set of steps to make a
successfully bootable fedora 28 image for my odroid hc2 computers.
the reason for this is several, but main one is to have all gluster related
packaged available like the samba vfs modules and iscsi related packages for
gluster that is missing from the ubuntu images.
plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try
to work around that by disabling it then boot takes maybe 5-10 minutes at least
with failing services (probably those that depend on network) and when i
finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working:
(this is done from a fedora 28 host)
1: first install needed packages
dnf install arm-image-installer-2.5-1.fc28.noarch
dnf install uboot-images-armv7-2018.03-6.fc28.noarch
2: get image and install it to sd card
--image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass
--media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd
cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
(sdf in this case is my sd card)
3: fix the missing dtb file
mount -t auto /dev/sdf2 /tmp/sd
ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb
4: make it boot by running sd_fusing
mkdir sd_fusing; cd sd_fusing
chmod a+x sd_fusing.sh
cp /usr/share/uboot/odroid-xu3/u-boot.bin .
ok so now comes the problems
at this stage i have a bootable image but it gets stuck, most likely on initial
setup that never shows up.
the thing is, it is not locked up because if i plug in an usb device i get a
few lines on the serial console so kernel is still working but boot is stuck.
last few lines on serial console is something like:
Starting firewalld - dynamic firewall daemon...
Starting Initial Setup configuration program...
then some stuff related to usb & my disk
then on first boot a few lines related to OpenSSH key generation
rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other
computer and remove the following two files:
this gets rid of the initial setup but then i get a whole bunch of services
failing and boot being really really slow, it takes probably 10-15 minutes for
everything to time out and get to the logon prompt.
when i get it root doesn't work.
this is where i kind of gave up.
i know i somehow managed to get a bootable image several months ago, but i'm
not sure if i then had to manually set root password by editing passwd or
shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work.
for example arm-image-installer with a board definition for odroid.
may be usefull even if we have to run sd_fusing manualy after anyway, possibly
with a text saying so.
this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file
dtb file for hc2, one that works and is appropriate.
I asked on linux-arm-kernel mail list regarding the "missing" dtb file problem
for odroid hc2.
The info i got was that the hc1 dtb file is the correct one to use for hc2 too
and there is a patch to make uboot detect and use the right dtb file.
The patch in question:
I rebuilt uboot-tools-2018.09-1.fc29.x86_64 with this patch applied and it
boots and uses the hc1 dtb file correctly.
No need for a manual symlink like:
ln -s exynos5422-odroidhc1.dtb exynos5422-odroidunknown.dtb
So would be nice if this could be considered for inclusion in the fedora uboot
package sometime in the future to make it easier to get the hc2 up and running.
Wifi on RPi 3B+ appears to no longer work after updating kernel to 4.18.17-300.fc29.aarch64.
Worked OK with 4.18.16-300.fc29.aarch64
dmesg | grep brcm
[ 19.386730] bluetooth hci0: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2
[ 19.396367] Bluetooth: hci0: BCM: Patch brcm/BCM4345C0.hcd not found
dmesg | grep brc
[ 30.062387] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 30.075952] usbcore: registered new interface driver brcmfmac
[ 30.169952] bluetooth hci0: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2
[ 30.169957] Bluetooth: hci0: BCM: Patch brcm/BCM4345C0.hcd not found
[ 32.183096] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 32.220167] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4
Has anyone had any luck getting Fedora 28 to work on the Odroid C2?
I've tried downloading the Fedora 28 Server aarch.raw.xz image which i
put onto my sd card. I then moved the Archlinux aarch64 boot parition
into boot along with the lib/modules and lib/firmware folders from
Archlinux. This has been to no avail. I'm working on building the
hardkernel kernel myself now but have never actually compiled a kernel
myself so I'm not sure what I fully need to get the Fedora rootfs to
boot with the kernel.
If anyone has some guidance or a nice writeup on getting a bootable
kernel recognized by Fedora on the Odroid C2 that would be greatly
I installed fedora en my cubieboard2, using a sdcard, and it runs OK.
Nevertheless, my idea was to execute it from its mmc disk.
I tried to follow exactly the same procedure as with the sdcard, writing uboot and then the distro using the dd command, but this time into the mmc, but nothing happens. If I try to boot the system after writing the mms, nothing happens, it does not even boot.
Does anyone knows how can I overcome this hurdle?
I try to boot ARM Fedora 29 or Rawhide on Lamobo R1 router and I connect
it by HDMI cable, but it does nothing, ethernet ports don't blink, the
device seems, that don't boot.
When I use old original Bananian image, then device boot up properly,
but Bananian is not developed now, so I want to use Fedora. I look
into dtb directory and I found Lamobo r1 dtb file, so what is wrong.
I installed Fedora 29 on a Udoo Neo ( i.MX ).
I tried to connect via Wi-Fi. It "associates", and the AP shows that
a DHCP offer is sent, but it times out.
This used to work in F28. Wired Enet works. USB Wi-Fi works on F29.
Attached is merged and sorted log files : dmesg (starts w/ square
bracket), NetworkManaged (with "neo0" tag), AP (with "daemon" tag).
Any tips ?