wzab/br_internet_radio

Simple Internet radio built using mpd/mpc and Flask with Buildroot

br_internet_radio's Issues

Cannot export GPIOs in Raspberry Pi

Hi. I read you connected GPIO in QEMU emulated machine to host. When I type in a shell on my raspberry pi:
sudo -s
echo 4 >/sys/class/gpio/export
I get the error
-bash: /sys/class/gpio/export No such file or directory
My bash script
#!/bin/sh
qemu-system-arm -machine versatilepb -cpu arm1176 -drive file=/home/user1/rootfs/2016-05-27-raspbian-jessie-lite.img -kernel kernel-qemu-4.4.34-jessie -m 256M -serial stdio -append "rw console=ttyAMA0 console=tty1 root=/dev/sda2 rootfstype=ext4 rootwait fsck.repair=yes memtest=1" -nic user,model=virtio-net-pci,ipv4=on,hostfwd=:127.0.0.1:45022-:22 -qtest unix:/tmp/tmp-gpio.sock

I tried many versions of Raspberry Pi and all of them give the same error.
Please, tell me how you made it working.

Version on Orange Pi Zero may start very slowly

The cause of the problem is lack of random values in the entropy pool.
It may take a few minutes before enough random values are collected and the secure network connections are possible...

Problem with initial state of the GPIOs

Due to the method how GUI and the emulated systems are connected, the initial state of LED may be not transferred correctly from the emulated machine to GUI and the initial state of buttons and switches may be not transferred correctly from GUI to the emulated machine.
I have added the "Reconnect" button in the GUI that toggles all inputs ans assures correct tracking of further changes. It also attempts to enforce the emulated machine to send the correct state of all the LEDs, but it does not work correctly.
At the moment, your emulated machine must toggle each LED (either in U-Boot or in Linux) to ensure that further changes of LED's state are correctly transferred.
Solving that issue probably requires redesign of the MPC8XXX model, using another emulated GPIO chip to provide virtual GPIOs, or switching from message based communication between GPIOs and GUI to shared memory (like in ivshmem in QEMU - https://github.com/qemu/qemu/blob/master/docs/specs/ivshmem-spec.txt ).

Control of interrupts has a problem

Simulation of GUI-connected GPIO in the "gpio" branch has certain problem.
The driver accepts only "none", "both" and "falling" as parameters defining the interrupt generation.
Additionally, "both" and "falling" give the same effect - interrupts are generated on both edges.