On 08/22/2018 04:24 PM, benxi wrote:
Hi Qi,
Thanks for your reply. It indeed solves the problem, however I'm
afraid that modifying SERIAL_CONSOLES can have side effects on other
recipes. I also wonder if there 're any way to enable ttyS0 on my
raspberry pi(Since ENABLE_UART doesn't work).
The SERIAL_CONSOLES setting is _expected_ affect all recipes. That's why
it's usually set in some .conf file.
Serial consoles will have different names and are device related. That's
why we have the variable SERIAL_CONSOLES.
I think you should just change SERIAL_CONSOLES to match the raspberry pi.
Best Regards,
Chen Qi
在 2018-08-22 15:59:44，"ChenQi" <qi.c...@windriver.com> 写道：
On 08/22/2018 12:24 PM, benxi wrote:
Hello Everyone,
I build a rpi-hwup-image and run it on my raspberry pi3(Model
B V1.2). After the system boots up, I keep seeing such message:
INIT: Id "S0" respawning too fast: disabled for 5 minutes.
I notice that yocto adds the following line to /etc/inittab
when install sysvinit, since Serial_Console was set in
raspberrypi3-64.conf:
S0:12345:respawn:/bin/start_getty 115200 ttyS0 vt102
I try to add ENABLE_UART = "1" in local.conf but the message
keeps coming. The message can be eliminated by commenting out the
corresponding line in /etc/inittab.
So, is this a bug of meta-raspberrypi? Is there anyway to fix
it without modifying sysvinit's recipes and /etc/inittab?
Could you please check the SERIAL_CONSOLES variable to see if
modifying its value could solve the problem?
Best Regards,
Chen Qi
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
