Re: [beagleboard] How to correctly power down BeagleBoard-xM ?

[João Manoel]

I used to use "sudo halt", but I found that using "sudo poweroff"
completely switches off the board, even the leds. I don't know why it is
different, but the poweroff command seems to tell the PMU to cut the power
line, and "halt" does only a software power off.

Best regards.

Em ter, 6 de ago de 2019 às 05:09, Jani  escreveu:

> How to proceed from here?  LED D5 and D14 are still ON.
>
> Do I just close the PC Console terminal?
>
> [image: halt.PNG]
>
>
> On Monday, August 5, 2019 at 3:18:02 PM UTC-4, Robert Heller wrote:
>>
>> At Mon, 5 Aug 2019 23:18:31 +0530 beagl...@googlegroups.com wrote:
>>
>> >
>> >
>> > Interesting. I thought shutdown command was the way to do it.
>>
>> /sbin/halt === /sbin/shutdown -h now
>> /sbin/reboot === /sbin/shutdown -r now
>>
>> /sbin/halt and /sbin/reboot are "shortcuts" for common shutdown cases.
>>
>> Feel free to type all of '/sbin/shutdown -h now' if you prefer...
>>
>> >
>> >
>> > On Mon, Aug 5, 2019 at 6:22 PM Robert Heller 
>> wrote:
>> >
>> > > At Sun, 4 Aug 2019 21:25:19 -0700 (PDT) beagl...@googlegroups.com
>> > > wrote:
>> > >
>> > > >
>> > > >
>> > > >
>> > > > I have my BeagleBoard-xM connected to Windows 10 Laptop.  They are
>> > > > communicating over serial console.
>> > > > I logged out and closed serial console.
>> > > >
>> > > > How should I correctly power down my board?
>> > >
>> > > *Before* you logout, run this command:
>> > >
>> > > sudo /sbin/halt
>> > >
>> > > This will cleanly shut the BeagleBoard down.
>> > >
>> > > >
>> > >
>> > > --
>> > > Robert Heller -- 978-544-6933
>> > > Deepwoods Software-- Custom Software Services
>> > > http://www.deepsoft.com/  -- Linux Administration Services
>> > > hel...@deepsoft.com   -- Webhosting Services
>> > >
>> > >
>> > > --
>> > > 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 beagl...@googlegroups.com.
>> > > To view this discussion on the web visit
>> > >
>> https://groups.google.com/d/msgid/beagleboard/20190805125147.BCF6926C009B%40sharky3.deepsoft.com
>> > > .
>> > >
>> >
>> >
>>
>> --
>> Robert Heller -- 978-544-6933
>> Deepwoods Software    -- Custom Software Services
>> http://www.deepsoft.com/  -- Linux Administration Services
>> hel...@deepsoft.com   -- Webhosting Services
>>
>>
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/230cc004-5173-499c-98e4-c30451d84f7f%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/230cc004-5173-499c-98e4-c30451d84f7f%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
João Manoel

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOe5q-Fyn-6YCbuTPKJv4u%2BrYU8asPFYXJTxsLZVPN4NsTkfOg%40mail.gmail.com.

[beagleboard] Re: pwm audio driver on BBB wireless with snd-pwmsp module

[João Manoel]

I want to say that I managed to get the pwm sound working.

I was wrong when I said that the pwm sound was on the pin P9.28, in fact, 
this pin is related to the i2s sound from the board that is actually 
connected to the HDMI ic for sound. This explains why the "sound" was very 
noise; I'm surprised that I could listen to it, it is a digital sound data. 
I think that with good filtering it is even possible to remove the noise 
part of it if you have a mono sound for a cheap sound, just thinking Or 
maybe just connect an i2s ic driver and have a good sound :)

Anyway, in this case, the pwmsp module was not even working. To solve this, 
and to not confuse, I added the following line to uEnv.txt:

disable_uboot_overlay_audio=1

This will disable the i2s sound. (I think)
I used the dtbo created from the dts that I attached in the previous 
message on uEnv.txt, and loaded the module with: 

sudo modprobe snd_pwmsp

My system was freezing when I tried to play any sound. I recompiled the pwmsp 
module with the debug option enabled, and I found that the problem was on the 
statement (atomic_set(>timer_active, 1); of the file pwmsp_lib.c

This problem was fixed adding the line: pm_runtime_irq_safe(>dev); to the 
*drivers/pwm/pwm-tiehrpwm.c* (like here 
<https://github.com/JoelGoh92/linux-2/commit/d355c57f41e81fd0b346db9e7ce62d3a2ee8deb0>).
  I recompiled the kernel and the pwm sound worked. I don't know if the line 
added to the pwm driver of the board can 

impact in something else.








Em quarta-feira, 17 de julho de 2019 17:49:15 UTC+2, João Manoel escreveu:
>
> Hi,
>
> I'm trying to make the pwmsp driver work on my board. The driver is 
> compiled as a module on the kernel 4.14 by default
>
> https://github.com/beagleboard/linux/tree/4.14/sound/drivers/pwmsp
>
> I managed to make the driver work when I remove cape universal from 
> uEnv.txt (commenting the line #enable_uboot_cape_universal=1), the sound 
> is very noisy even with an RC low pass filter, but somehow it works. The 
> sound can be collected from pin P9.28, and it is recognized in ALSA as a 
> sound card.
>
> I have a LCD cape that I want to use, but when I connect my LCD to the 
> board the pwmsp driver doesn't load anymore. My LCD cape uses the same pin 
> P9.28 to control the brightness.
>
> I tried to recompile the dtbo used in my LCD removing the brightness 
> option leaving the pin completely free, but the pwmsp driver still not 
> loading, even when I force u-boot to not load the dtbo of the lcd (with 
> disable_uboot_overlay_addr0=1). I also tried to make my own dtbo file to 
> load the pwmsp driver but it also doesn't work, and the system crashes when 
> I try to play a sound.
>
> My question is how I change the PWM pin used by *pwmsp* to use as audio 
> output.
>
> My lcd module uses this dts:
>
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAPE-DISP-CT4-00A0.dts
>
> The dts that I tried to make to change the pwm port for pwmsp:
>
> /dts-v1/;
> /plugin/;
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black";
>
> /* identification */
> part-number = "BB-SND-PWM1";
> version = "00A0";
>
> /* state the resources this cape uses */
> exclusive-use =
> "P9.14",
> "P9.16";
>
> /*
>  * Free up the pins used by the cape from the pinmux helpers.
>  */
> fragment@0 {
> target = <>;
> __overlay__ {
> P9_14_pinmux { status = "disabled"; };  /* (U14) 
> gpmc_a2.ehrpwm1A */
> P9_16_pinmux { status = "disabled"; };  /* (T14) 
> gpmc_a3.ehrpwm1B */
> };
> };
>
> fragment@1 {
> target = <_pinmux>;
> __overlay__ {
> bb_pwm1_pin: pinmux-pwm1-pin {
> pinctrl-single,pins = <
> 0x48 0x06 /* (U14) 
> gpmc_a2.ehrpwm1A */
> 0x4c 0x06 /* (B17) 
> gpmc_a3.ehrpwm1B */
> >;
> };
> };
> };
>
> fragment@2 {
> target = <>;
> __overlay__ {
> bb_pwm1_test_helper: bb_snd-pwm1 {
> compatible = "bone-pinmux-helper";
> pinctrl-names = "default";
> pinctrl-0 = <_pwm1_pin>;
> 

[beagleboard] Re: How can I enable audio (i2s) with a LCD screen?

[João Manoel]

I could get the i2s with my LCD adding this line to uEnv.txt:

uboot_overlay_addr0=/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo

Doing this, I am making the LCD-HDMI converter work, and not allow the 
BB-CAPE-DISP-CT4 load. As my LCD is connected to the same pins that the 
HDMI converter is connected, my LCD just works.

I now have an HDMI output, and the LCD working at the same time with i2s 
audio on the right pins.

I don't think that this is the best solution, this is just a turn around to 
make it works. I also forced a resolution to match with my LCD with the 
line:

cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:480x272M@60e

With this, my HDMI video doesn't work, because the resolution is not 
compatible, but my LCD still working, and I still have i2s audio.

If someone knows a better solution for this, please, let me know.

I tried to recompile the dtbo of my LCD adding some of the fragments from 
the HDMI overlay mentioned, but I couldn't make it work. I couldn't find a 
good documentation about how these overlays, and device trees works on the 
board.

If someone can point me good documentation about it I will appreciate.

I'm posting it because I think that there is so little documentation for 
beginners about the BeagleBoard that anything can help someone that is a 
bit lost. Even simple things on this board are complicated and the 
documentation that you can find are most of them outdated with the old cape 
system, that doesn't work anymore. This just confuses the people.

Thank you


Em domingo, 21 de julho de 2019 19:08:50 UTC+2, João Manoel escreveu:
>
> Hi,
>
> I have a BBB wireless with the lastest IoT Debian image.
> When I don't have an HDMI screen connected to my board I can take a sound 
> output via i2s on the pins P9.28, P9.29, and P9.31, and ALSA lists a sound 
> device:
>
> [ 2.913839] ALSA device list:
> [ 2.916851] #0: TI BeagleBone Black
>
> When I connect my LCD cape to the board the sound device disappears, even 
> when I disable the cape on uEnv.txt with: disable_uboot_overlay_addr0=1
>
> I would like to know how can I force enable an i2s audio output with my 
> LCD screen attached. Originally my cape uses the pins P9.28, P9.29, and 
> P9.31 (BB-CAPE-DISP-CT4-00A0.dts 
> <https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAPE-DISP-CT4-00A0.dts>)
>  
> to control the touch and the backlight, but I slightly modified the dts to 
> not use these pins. But even with the cape completely disabled in the 
> uEnv.txt I don't have sound. Am I disabling it correctly? How to force 
> enable audio out?
>
> Best regards,
>
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d446c461-feb4-4a6f-b810-8cb0f3d1bfb8%40googlegroups.com.

[beagleboard] How can I enable audio (i2s) with a LCD screen?

[João Manoel]

Hi,

I have a BBB wireless with the lastest IoT Debian image.
When I don't have an HDMI screen connected to my board I can take a sound 
output via i2s on the pins P9.28, P9.29, and P9.31, and ALSA lists a sound 
device:

[ 2.913839] ALSA device list:
[ 2.916851] #0: TI BeagleBone Black

When I connect my LCD cape to the board the sound device disappears, even 
when I disable the cape on uEnv.txt with: disable_uboot_overlay_addr0=1

I would like to know how can I force enable an i2s audio output with my LCD 
screen attached. Originally my cape uses the pins P9.28, P9.29, and P9.31 (
BB-CAPE-DISP-CT4-00A0.dts 
)
 
to control the touch and the backlight, but I slightly modified the dts to 
not use these pins. But even with the cape completely disabled in the 
uEnv.txt I don't have sound. Am I disabling it correctly? How to force 
enable audio out?

Best regards,



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/53fcd56c-a2a5-4371-a358-0d3872f51937%40googlegroups.com.

[beagleboard] pwm audio driver on BBB wireless with snd-pwmsp module

[João Manoel]

Hi,

I'm trying to make the pwmsp driver work on my board. The driver is 
compiled as a module on the kernel 4.14 by default

https://github.com/beagleboard/linux/tree/4.14/sound/drivers/pwmsp

I managed to make the driver work when I remove cape universal from 
uEnv.txt (commenting the line #enable_uboot_cape_universal=1), the sound is 
very noisy even with an RC low pass filter, but somehow it works. The sound 
can be collected from pin P9.28, and it is recognized in ALSA as a sound 
card.

I have a LCD cape that I want to use, but when I connect my LCD to the 
board the pwmsp driver doesn't load anymore. My LCD cape uses the same pin 
P9.28 to control the brightness.

I tried to recompile the dtbo used in my LCD removing the brightness option 
leaving the pin completely free, but the pwmsp driver still not loading, 
even when I force u-boot to not load the dtbo of the lcd (with 
disable_uboot_overlay_addr0=1). I also tried to make my own dtbo file to 
load the pwmsp driver but it also doesn't work, and the system crashes when 
I try to play a sound.

My question is how I change the PWM pin used by *pwmsp* to use as audio 
output.

My lcd module uses this dts:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAPE-DISP-CT4-00A0.dts

The dts that I tried to make to change the pwm port for pwmsp:

/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "BB-SND-PWM1";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
"P9.14",
"P9.16";

/*
 * Free up the pins used by the cape from the pinmux helpers.
 */
fragment@0 {
target = <>;
__overlay__ {
P9_14_pinmux { status = "disabled"; };  /* (U14) 
gpmc_a2.ehrpwm1A */
P9_16_pinmux { status = "disabled"; };  /* (T14) 
gpmc_a3.ehrpwm1B */
};
};

fragment@1 {
target = <_pinmux>;
__overlay__ {
bb_pwm1_pin: pinmux-pwm1-pin {
pinctrl-single,pins = <
0x48 0x06 /* (U14) gpmc_a2.ehrpwm1A 
*/
0x4c 0x06 /* (B17) gpmc_a3.ehrpwm1B 
*/
>;
};
};
};

fragment@2 {
target = <>;
__overlay__ {
bb_pwm1_test_helper: bb_snd-pwm1 {
compatible = "bone-pinmux-helper";
pinctrl-names = "default";
pinctrl-0 = <_pwm1_pin>;
status = "okay";
};
};
};

fragment@3 {
target = <>;
__overlay__ {
status = "okay";
};
};


fragment@4 {
target = <>;
__overlay__ {
status = "okay";
};
};

/*
 * Load ALSA driver for piezo
 */
fragment@5 {
target-path="/";
__overlay__ {
sndpwm {
compatible = "snd-pwmsp";
pwms = < 1 0 0>;
status = "okay";
};
};
};
};

I couldn't find any documentation about this driver, and how to operate it.

I'm using the kernel:

Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 2018 
armv7l GNU/Linux

Thanks a lot if someone can help me ;)

Best regards,




-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e0dbc9f5-9637-4c67-89e2-13f032610c9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Compiling kernel for fbdev and removing DRM support

[João Manoel]

Just to tell that I managed to run Retroarch (surprisingly well!!) on my 
board with the stock kernel. But only inside an X environment with SDL 
support (not SDL2) .

Best,
Em sábado, 13 de julho de 2019 22:09:36 UTC+2, João Manoel escreveu:
>
> Hi Robert,
>
> thank you for your message. I used the configuration from bb.org_defconfig 
> and compiled again the kernel. I noticed that the default configuration 
> enables CONFIG_DRM_FBDEV_EMULATION by default. I compiled the kernel, and 
> I have video out to my LCD screen, but I still have problems with Retroarch 
> to run on my board.
>
> As this fbdev emulation is a default configuration I returned to the 
> original kernel (4.14.71-ti-r80) and now I don't really know why I cannot 
> run Retroarch with the standard video support on my board.
>
> I installed retroarch from the repository with (apt-get install retroarch) 
> in a clean Debian 9.5 IOT image. I had video error problems, so I followed 
> the instructions from here:
>
> https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston
>
> to install the accelerated video driver, and I managed to get the 3D 
> examples working nicely. But I still getting errors on the Retroarch log:
> ---
> 
> RetroArch [INFO] :: [DRM]: Mode 0: (480x272) 480 x 272, 59 Hz
> gbm: failed to open any driver (search paths 
> /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
> gbm: Last dlopen error: /usr/lib/dri/tilcdc_dri.so: cannot open shared 
> object file: No such file or directory
> failed to load driver: tilcdc
> RetroArch [INFO] :: Found GL context: kms
> RetroArch [INFO] :: Detecting screen resolution 480x272.
> RetroArch [INFO] :: [EGL]: EGL version: 1.4
> Segmentation fault
> --
>
> Now Retroarch seems to be able to detect the video configurations but 
> still giving errors, and craches.
>
> I also tried to compile retroarch from the source with more video driver 
> support like SDL, SDL2, and I found that they have an old driver dedicated 
> to OMAP processors from 2014 that needs /sys/devices/platform/omapdss 
> populated (
> https://github.com/libretro/RetroArch/blob/master/README-OMAP.md), but 
> none of the drivers that I tried worked. This driver was probably written 
> before DRM support to the beaglebone boards. So, that's why I would like to 
> have the standard fbdev working without any acceleration driver to test the 
> program. I expect that Retroarch won't work well with the PowerVR GPU 
> anyway.
>
> I tried to use old debian images but all images with the beagleboneblack 
> wireless support already have the DRM enabled, and with the 
> CONFIG_DRM_FBDEV_EMULATION enabled I'm confused, and I don't nkow how to 
> make Retroarch work.
>
> Do you have any suggestion?
>
> Best regards 
>
>
> Em sábado, 13 de julho de 2019 19:23:30 UTC+2, RobertCNelson escreveu:
>>
>> On Sat, Jul 13, 2019 at 3:54 AM João Manoel  wrote: 
>> > 
>> > Hi, 
>> > 
>> > I would like to make a program that uses the fbdev to work and I need 
>> to compile the kernel to add this functionality and remove the DRM support. 
>> > I managed to compile a bootable kernel but I'm failing to get the fbdev 
>> working. I would like to know what is the easiest way to get the fbdev 
>> working. 
>> > 
>> > The things that I modified to the kernel config are: 
>> > 
>> > - enable: 
>> > CONFIG_FB_DA8XX=y 
>> > - disable: 
>> > CONFIG_DRM 
>> > CONFIG_DRM_I2C_NXP_TDA998X 
>> > CONFIG_DRM_TILCDC 
>> > 
>> > What is missing to get video out with fbdev? 
>> > 
>> > My board is a Beagleboard black wireless, and I couldn't see any error 
>> on the dmesg or anything related to the video after booting without video. 
>> I'm compiling the kernel 4.14.108. I have an HDMI cable attached, but I'm 
>> also trying to get video out with an LCD cape (from farnell element14) 
>> > 
>> > Thank you in advance for the help :) 
>>
>> CONFIG_DRM_FBDEV_EMULATION 
>>
>> Then re-enable: 
>>
>> CONFIG_DRM 
>> CONFIG_DRM_I2C_NXP_TDA998X 
>> CONFIG_DRM_TILCDC 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0e9f77ba-03ca-4be4-a27a-5d5c22f04d58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Compiling kernel for fbdev and removing DRM support

[João Manoel]

Hi Robert,

thank you for your message. I used the configuration from bb.org_defconfig 
and compiled again the kernel. I noticed that the default configuration 
enables CONFIG_DRM_FBDEV_EMULATION by default. I compiled the kernel, and I 
have video out to my LCD screen, but I still have problems with Retroarch 
to run on my board.

As this fbdev emulation is a default configuration I returned to the 
original kernel (4.14.71-ti-r80) and now I don't really know why I cannot 
run Retroarch with the standard video support on my board.

I installed retroarch from the repository with (apt-get install retroarch) 
in a clean Debian 9.5 IOT image. I had video error problems, so I followed 
the instructions from here:

https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston

to install the accelerated video driver, and I managed to get the 3D 
examples working nicely. But I still getting errors on the Retroarch log:
---

RetroArch [INFO] :: [DRM]: Mode 0: (480x272) 480 x 272, 59 Hz
gbm: failed to open any driver (search paths 
/usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/tilcdc_dri.so: cannot open shared 
object file: No such file or directory
failed to load driver: tilcdc
RetroArch [INFO] :: Found GL context: kms
RetroArch [INFO] :: Detecting screen resolution 480x272.
RetroArch [INFO] :: [EGL]: EGL version: 1.4
Segmentation fault
--

Now Retroarch seems to be able to detect the video configurations but still 
giving errors, and craches.

I also tried to compile retroarch from the source with more video driver 
support like SDL, SDL2, and I found that they have an old driver dedicated 
to OMAP processors from 2014 that needs /sys/devices/platform/omapdss 
populated (https://github.com/libretro/RetroArch/blob/master/README-OMAP.md), 
but none of the drivers that I tried worked. This driver was probably 
written before DRM support to the beaglebone boards. So, that's why I would 
like to have the standard fbdev working without any acceleration driver to 
test the program. I expect that Retroarch won't work well with the PowerVR 
GPU anyway.

I tried to use old debian images but all images with the beagleboneblack 
wireless support already have the DRM enabled, and with the 
CONFIG_DRM_FBDEV_EMULATION enabled I'm confused, and I don't nkow how to 
make Retroarch work.

Do you have any suggestion?

Best regards 


Em sábado, 13 de julho de 2019 19:23:30 UTC+2, RobertCNelson escreveu:
>
> On Sat, Jul 13, 2019 at 3:54 AM João Manoel  > wrote: 
> > 
> > Hi, 
> > 
> > I would like to make a program that uses the fbdev to work and I need to 
> compile the kernel to add this functionality and remove the DRM support. 
> > I managed to compile a bootable kernel but I'm failing to get the fbdev 
> working. I would like to know what is the easiest way to get the fbdev 
> working. 
> > 
> > The things that I modified to the kernel config are: 
> > 
> > - enable: 
> > CONFIG_FB_DA8XX=y 
> > - disable: 
> > CONFIG_DRM 
> > CONFIG_DRM_I2C_NXP_TDA998X 
> > CONFIG_DRM_TILCDC 
> > 
> > What is missing to get video out with fbdev? 
> > 
> > My board is a Beagleboard black wireless, and I couldn't see any error 
> on the dmesg or anything related to the video after booting without video. 
> I'm compiling the kernel 4.14.108. I have an HDMI cable attached, but I'm 
> also trying to get video out with an LCD cape (from farnell element14) 
> > 
> > Thank you in advance for the help :) 
>
> CONFIG_DRM_FBDEV_EMULATION 
>
> Then re-enable: 
>
> CONFIG_DRM 
> CONFIG_DRM_I2C_NXP_TDA998X 
> CONFIG_DRM_TILCDC 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8dc35a7d-0b64-4a54-9a47-63b1da104ceb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Compiling kernel for fbdev and removing DRM support

[João Manoel]

Hi,

I would like to make a program that uses the fbdev to work and I need to 
compile the kernel to add this functionality and remove the DRM support.
I managed to compile a bootable kernel but I'm failing to get the fbdev 
working. I would like to know what is the easiest way to get the fbdev 
working.

The things that I modified to the kernel config are:

- enable: 
CONFIG_FB_DA8XX=y 
- disable: 
CONFIG_DRM 
CONFIG_DRM_I2C_NXP_TDA998X
CONFIG_DRM_TILCDC

What is missing to get video out with fbdev?

My board is a Beagleboard black wireless, and I couldn't see any error on 
the dmesg or anything related to the video after booting without video. I'm 
compiling the kernel 4.14.108. I have an HDMI cable attached, but I'm also 
trying to get video out with an LCD cape (from farnell element14)

Thank you in advance for the help :)

Best regards 

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/699739b8-579d-410b-ac44-105bd364c010%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PB LCD

[João Manoel]

Hi Dan,

thank you to share your project, really nice :)

I saw that you used the standard pocketbeagle. I also noticed that you are 
the author of a hackday.io article about the PMU inside the pocketbeagle 
which I'm also interested in that.

Like you, I also have a project that uses the Rpi zero, and I needed to 
stop working on that due to the workarounds that I had to do to make it a 
portable system. The Rpi doesn't support any kind of low power modes 
(sleep, suspend to RAM ...), doesn't have PMU and we have to use SPI or 
HDMI to drive an LCD display which is a problem in performance, and power 
efficiency.

I saw on the beagleboards a light because we have the PMU, and an LCD 
driver ready to use without any proprietary firmware, I don't need HDMI 
output and I don't want to waste power to feed HDMI IC's. Everything with a 
trully open hardware system is a dream! Also with the Octavo system in a 
package, I could design a more professional system without been too complex 
for a hobbyist point of view, and maybe I could even try to solder the BGA 
chip myself. So, now I have space to work in my software and If everything 
goes well I could even try to go to a customized board. 

So, the pocketbeagle seemed a good start to work, but the lack of the LCD 
pins and the things that you mentioned in your article about the PMU really 
broke my legs. The BBB (standard, and Wireless) are big boards, has many 
things that I don't need and will consume my power resources. Would be a 
good addition to have wifi (and switch it off when it is not needed), but 
the wireless version doesn't have wifi when working on battery

When my boards arrive, next week, I will work on the BBB wireless before, 
and in the future, I will try to hook some wires from the resistors that 
configure the boot, and see if I can drive an RGB LCD. I really don't want 
to go to SPI LCD's for now, maybe just to try.

Have a good weekend.

Best regards,


Em sábado, 6 de julho de 2019 16:43:17 UTC+2, Dan Julio escreveu:
>
> Although it isn't the 4.3" CAPE, I have gotten a generic and inexpensive 
> 2.8" ILI9348-based SPI display to work with the Pocketbeagle (and 
> Beaglebone black).  It seems reasonably fast although I'm sure not as fast 
> as the parallel display.  I haven't yet gotten the built-in TSC2046 
> resistive touch controller to work yet.  I've attached the dts file for the 
> display.  You can see how I wired it up at the following github page:
>
> https://github.com/danjulio/lepton/tree/master/pocketbeagle
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f25131c9-584d-44b4-bee0-ef67e93af374%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.