Hi, I have code that builds to different FX30 modems and with different versions of legato. The name for the uart seems to change from device to device and legato version. How can I work out what dev name I should be using per device/legato version? I need to build it into my build system. I have …

I got it to work again… by flashing not the stock FW, but the intermediate one you linked above… At this point the mapping was still wrong… but I changed the mode to AT!MAPUART=15,1 then rebooted and ran AT!MAPUART=17,1 then rebooted then my mapping as correct again…

You need to have a list to match with different module and firmware

Yes, but what is that list… what version of what FW causes the change in naming? I know that the following guide suggest a change to the MSMx naming Linux 4.14 Migration Guide - Legato Docs … but what about the other naming differences… HS0 and HSL0?

Does this help? [image] Issue with stty config and reception of data in FX30 FX30 Hi Mike, Both console and custom linux application use HSL0, could you please double check? HS0 should not be enabled. The Custom Linux application is a mode that keeps the port open but d…

Yes I am aware of mapuart. AT!MAPUART? return 17,0… for some reason I have the same problem descripbed in the link. only ttyHS0 is available in /dev/ not /ttyHSLO Any ideas how I revert it back. I assumed my problem was with FW versions… but maybe this device has got itself in a mess… dmesg | gre…

I found this in the latest user guide (update 2 weeks ago)… which suggest something has gone wrong with port mappings… I have never put it into the mode 15… so not sure how it has gone wrong… o set: AT!MAPUART=[,] where: • can be: 0—UART disabled 1—AT Command service (Note: Not available for …

I remember I tried this before: FX30(WP77 inside) (FW: R14) AT!MAPUART=17,1 → /dev/ttyHSL0 AT!MAPUART=15,1 → /dev/ttyHS0

Yes I know that is what the documentation I linked above says. But that is NOT what is happening on my module. It is going to AT!MAPUART=17,1 → /dev/ttyHS0 when it should rather be AT!MAPUART=17,1 → /dev/ttyHSL0 according to the docs… so something is not right on my module. I have tried flashing th…

are you using the WP7607 which having old memory with the official R14.1 full imge instead of the yocto image built by yourself?

No this is the WP7611-1 module I have two running… one is correct and using HSL0… but this one is somehow got itself stuck on HS0… I am sure it used to work with HSL0… I wonder if all the attempts of getting FW download to work has caused some conflicts with version changes etc… Also it is notable…

are you using the yocto image built by yourself? if you have one OK WP7611 and one NOK WP7611, have you compared ati3 and ati8 to figure what makes the difference?

UART name per legato version / FX30 version

jyijyi March 30, 2023, 1:13pm 4

Does this help?

It depends on at!mapuart setting

Topic		Replies	Views
FX30s - Using UART1 & 2 in legato app FX30	5	1127	June 28, 2019
UART1 with Beta 14.07	3	2407	October 20, 2014
FX30S : HSL0 or HS0 FX30	1	870	August 2, 2019
WP7702-FX30S R15.1 missing /dev/ttyGS0 WP Series	12	589	June 2, 2023
Which tty for which UART? WP Series	8	5849	October 19, 2015

UART name per legato version / FX30 version

Related topics