Re: [beagleboard] Ubuntu 16.04.4 unable to load desktop from eMMC

Which is your recommendation? BR! El lunes, 13 de febrero de 2017, 23:43:09 (UTC+1), RobertCNelson escribió: > > On Mon, Feb 13, 2017 at 4:13 PM, wrote: > > After flashing into the eMMC the last Ubuntu 16.04.4, > > BBB boots up connected through HDMI to the TV, but no

[beagleboard] Ubuntu 16.04.4 unable to load desktop from eMMC

After flashing into the eMMC the last Ubuntu 16.04.4, BBB boots up connected through HDMI to the TV, but no more than the terminal is shown at the display. - Does Ubuntu include the desktop environment? - If not, can it be installed easily? Which desktop is your recommendation? -

[beagleboard] Re: BES v0.8 does not recognize the USB Gamepad

You're right, the link was wrong, but that is the USB gamepad. The BBB is sourced by a power supply (5V, 2A) but maybe the low-cost gamepad is the root cause of the issue, because no USB device is detected. I keep looking for a solution, and if there is none, I will buy a better gamepad.

[beagleboard] Re: BES v0.8 does not recognize the USB Gamepad

Dear Andrew, thank you very much for your answer. I can stabilize the image at home screen with the HW workaround, but gamepads are not working yet. Through web server, I configured the controllers but no action is performed when pressing any button or combination of buttons. Can you imagine

[beagleboard] BES v0.8 does not recognize the USB Gamepad

Does anybody know how can I add the support for these USB gamepads? It would be great to have some help for doing this, even if someone could explain how develop a new driver and compile It. I have everything ready but the USB gamepads. -- For more options, visit

[beagleboard] BES v0.8 does not recognize the USB Gamepad

Now, I have been trying to find out what it is happening with the BES after flashing the v0.8 in a new uSD card. The main issue is with the USB controller , let me explain what I have found. Just flashed

[beagleboard] Re: BeagleSNES does not recognize USB gamepad connected to native BBB usb

Could you finally use the USB gamepad? I have the same issue, and I can not make the BBB recognize the USB Gamepad, while the PC detect it both in Windows and Linux. I would like to know any way to solve the issue. El martes, 19 de enero de 2016, 18:58:54 (UTC+1), Wagner Gomes escribió: > >

[beagleboard] System can not boot due to missing initrd.img file

Flashing a new Debian image to the Beaglebone Black, it crashed due to a power outage. After the incident, the Beaglebone does not boot (at boot time, the four LEDs stay lit), nor can be flashed. Connecting to serial port, I can watch the boot logs and enter to U-Boot terminal. The boot logs

[beagleboard] Flash eMMC from uSD with higher capacity

With a Debian distro installed into a 8GB uSD (but uSD memory is almost free), I need to flash this distro to eMMC. - The S2 switch button only works to start the BeagleBone Black from the uSD, and not for flashing the distro into eMMC. - Distro has no included any tool for flashing eMMC. So,

Re: [beagleboard] Debian 8.4. Kernel Files Missing

Thanks!! It's done! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[beagleboard] Debian 8.4. Kernel Files Missing

After flashing Debian 8.4 image to BeagleBone Black, I have update the kernel through script tool '*/opt/scripts/tools/update_kernel.sh*' to " *4.4.12-bone11*" kernel version. Then, I have built a new kernel from 4.7 branch with RobertCNelson tools ' *build_kernel.sh*'. Now, I have all files

[beagleboard] Debian 8.4. Upgrading kernel.

After flashing Debian 8.4 image to BeagleBone Black, I have update the kernel through script tool '*/opt/scripts/tools/update_kernel.sh*' to " *4.4.12-bone11*" kernel version. Then, I have built a new kernel from 4.7 branch with RobertCNelson tools ' *build_kernel.sh*'. Now, I have all files

[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support

I have the chipsee 7" capacitive lcd v2 with speaker, and I'm trying to work with debian image from chipsee, apart from some issues I have found in the distro, I would like to know how I can change the switches behaviour for volume up/down and brightness up/down. Searching about it, I have

Re: [beagleboard] BeagleBone Black Kernel Main Differences

Thanks all!! I'm looking for a kernel that allow me to control a screen with touchpanel and a integrated speaker (I have published a concrete thread for this without any response yet), so understansing the differences between kernels could help me to know which is the best for my application,

[beagleboard] BeagleBone Black Kernel Main Differences

These are a newbie questions, but it would be fine if a wiki exists with clear explanantion about. - Which are the main differences between branches (ex. v4.1 vs v4.4)? - Which are the features of every kernel branch (ex. v4.4)? - What are the differences between 'bone-kernel',

Re: [beagleboard] Re: BBB, how to install chipsee 7inch screen and gfx driver with lastet debian image?

Taking advantage of the thread, I would like to make a question in reference to both, Chipsee TFT & BBB. @Damian, does your system work fine just installed? I have followed the instructions wrote here (except the SGX ones, by the moment I'm not going further), but the touch panel does not work

[beagleboard] Audio & Calibration Chipsee Issue

After installing Debian Jessie 8.4 into the BeagleBone Black, and making the proper configuration, desktop environment is shown into Chipsee screen. But there are two different issues, audio and calibration, where we need your help to solve them. 1. Calibration Issue: *Touch panel detects

Re: [beagleboard] Adding cape support for new kernel and homemade cape

Thanks Robert! Capemgr added, now it is time to make my own one. KR! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it,

[beagleboard] Adding cape support for new kernel and homemade cape

My BBB has to communicate with a new homemade cape, which has different I2C sensors and a MCU controlled by UART. The BBB has a Debian 7.8 distro, Debian 4.6.3-14, with 4.1.18-ti-r56 kernel. Then, I need to add cape support into capemgr in order to work with the cape. Looking for some info, I

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Launching alsaplayer, *wav *and *mp3 *files can be played, but no sound is reproduced. It seems as the BeagleBone's drivers are not pointing to right audio interface. *How can I checked if the SoC's audio codec and the HDMI's interface are configured and working fine?* By the moment, I can't

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Going forward in my test: - Current kernel: *4.1.18-ti-r56* - *aplay -L*: null Discard all samples (playback) or generate zero samples (capture) default:CARD=Black TI BeagleBone Black, Default Audio Device sysdefault:CARD=Black TI BeagleBone Black, Default Audio Device -

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

*Any hint/tip?* -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Kernel is updated to TI's branch: "*4.1.15-ti-r40*". Now, VLC player does not show any error message and plays the sound sample, but no sound is reproduced. I have checked the basics, volume, mute option and similar. These are not the failures. *Which could the missing part for making the

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Kernel is updated to TI's branch: "*4.1.15-ti-r40*". Now, VLC player does not show any error message and plays the sound sample, but no sound is reproduced. I have checked the basics, volume, mute option and similar. These are not the failures. Which could the missing part for making the sound

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Thanks Robert! I have an issue with ntp update at boot. I have solved it temporary. Well, I have just tried to launch the '*update_kernel*' script: cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh --ti-channel --lts-4_1 But it fails due to there is not space left on device. cp:

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Moreover, if I follow next steps: cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh --ti-channel --lts-4_1 I get this message: ERROR: The certificate of 'rcn-ee.com' is not trusted. The certificate has not yet been activated. -- For more options, visit

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

I have checked that the current resolution from BeagleBone's HDMI is: *1280x720@60e* (*/boot/uboot/uEnv.txt*) I'm working with "4.1.x" kernel modified to support all multitouch screens. So, if I update the kernel from ti branch, I suspect I lose the kernel's modifications to support the

[beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

Adding new information about the issue: 'lsmod': snd 56846 6 snd_soc_core, snd_timer, snd_pcm, snd_seq, snd_seq_device, snd_comp 'modinfo snd': filename: /lib/modules/4.1.16-bone18/kernel/sound/core/snd.kp alias: char-major-116-* license:

[beagleboard] Play audio throuhg HDMI on BeagleBone Black

After work with a multitouch screen for the BeagleBone Black, now I just want to play audio/sounds through the HDMI connection as the multitouch screen has a speaker. First of all, I just copied an audio sample, and try to reproduce it by 'vlc', but next message is shown: "*Audio

[beagleboard] Re: Install kernel permanently - Issue

PD. To understand what I have done, I share here a link to the manual I have used to build & install the kernel. KR! -- For more options, visit http://beagleboard.org/discuss --- You received this message because

[beagleboard] Install kernel permanently - Issue

Hi all, I have built and installed a new kernel (4.1.16-bone18) for BeagleBone Black. After the installation, with 'uname -a', the output is right "... 4.1.16-bone18 ...", but as soon as a reboot is done, the previous kernel is reloaded. In this case, BBB returns to original kernel, "...

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Hi, I have just commented both lines, and the process goes well until console starts to show: *INIT: Id "T0" respawning too fast: disabled for 5 minutes* Then, the process enters into an infinite loop showing message every 5 minutes. What process is T0? And how can I solved this? KR!

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Hi, this is my original '*/etc/inittab*' file: Could I modify any file of my system (BBB)? Or may I need to re-built the kernel? KR! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Hi, this is my original '*/etc/inittab*' file: *T0:23:respawn:/sbin/getty -L ttyO0 115200 vt102* Could I modify any file of my system (BBB)? Or may I need to re-built the kernel? KR! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Finally... it works!!! Thanks Robert!!! -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Following this tutorial , kernel downloading could be started, but there have been some errors during the installation and finally it fails. *U-Boot# bootz ${loadaddr} - ${fdtaddr}* *Kernel image @ 0x8200 [

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

*libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.16-bone18/modules.dep.bin'* This error has been fixed after copying the '4.1.16-bone18' modules to ' */lib/modules*' path. */etc/rc.local: 14: /etc/rc.local: cannot create

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Thanks @jhon3909!! That is a complete guide, but I don't want to change the complete OS, just Kernel. I will avoid the microSD option by the moment. In future, I am sure that in future I will make a fresh installation, so it will be helpful. Here is the ouput I have got: *U-Boot# tftp

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Now, I have followed these other steps . I have built the kernel, uImage, and with the help of tftp uploaded it to BBB. Then, with 'bootm 0x8020' instruction, I forced the boot of the BBB with new kernel. But the results is: "spl_load_image_fat_os:

[beagleboard] Building Kernel with cross-compiler and sharing through USB

Hi all, finally I have launched myself to build a new kernel for my BeaglBone Black, as this is my first time, I have read lot of links and follow the steps proposed at some of them. I have been able to cconfigure and compile the kernel, but there is no way to upload the kernel to target,

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Hi, I have done it from Windows with Open tftp, but the process failed. tftpboot 0x80F8 am335x-boneblack.dtb tftpboot 0x80007FC0 uImage setenv bootargs console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait bootm 0x80007FC0 - 0x80F8 All works until last step which

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Hi, I have done it from Windows with Open tftp, but the process failed. tftpboot 0x80F8 am335x-boneblack.dtb tftpboot 0x80007FC0 uImage setenv bootargs console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait bootm 0x80007FC0 - 0x80F8 All works until last step which