cancel
Showing results for 
Search instead for 
Did you mean: 

systemd didn't generate a "dev-ttySTM0.device" unit, and therefore stopped getty

SMich.1
Senior

Hi, 

i moved to new ecosystem v2.0 "dunfell" and added my layers of wifi,camera, openCV and python packages from old Yocto ecosystem. 

first boot serial-getty@ttySTM0 working fine. 

on second boot it died and in /var/log/messeges i got: 

Unit serial-getty@ttySTM0.service is bound to inactive unit dev-ttySTM0.device. Stopping, too

I can't understand what i did wrong in Yocto layers that making this bug. 

 did someone had this issue?

4 REPLIES 4
Olivier GALLIEN
ST Employee

Hi @SMich.1​ 

Did you take complete and consistent ecosystem v2.0 "dunfell" components version ?

I understand you keep openCV and python package version similar to old "thud" version, right ?

Please double check there is no compatibility problem. I would recommend to upgrade on dunfell version for all those packages.

Hope it help,

Olivier

Olivier GALLIEN
In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
SMich.1
Senior
  1. i using all new components of dunfell
  2. i switched to new package versions of .

i did added new distro and machine. but everything else working

SMich.1
Senior

what i can check in yocto layers that may help me?

SMich.1
Senior

I found that in file /extlinux/extlinux.conf ihave:

APPEND root=PARTUUID=491f6117-415d-4f53-88c9-6e0de54deac6 rootwait rw console=ttySTM0,115200

but still the console=ttySTM0,115200 not passed to Getty service ...

so I just did:

vi /boot/extlinux/extlinux.conf

added space after 115200

resaved the file and now the ttySTM0 passed to Getty service.

First of all the problem was not with the v2.0 "dunfell" . it something with my yocto layers config . somebody can help?