i was able to update one GM02SP using the SFU, i am trying a different GM02SP the same way using only uart TX/RX at 1.8v logic level. using a logic analyzer i can see request/responses at baud rate 115200 to the messages to detect the cell modem. are there any specific requirements for the SFU that i am missing? like any specific usb UART to use, a better way to detect what the SFU is having trouble detecting, or maybe requirements for connecting a SFU to a usb UART
below is the logic level data at baud rate 115200, it is responding with “ok” “ok” “error” “error” and finally “ok” again
Did you face any error when did SFU upgrade? What’s the sfu upgrade message did you get? Upgrade sucess or upgrade fail? It would be helpful if you have the complete SFU upgrade log.
What kind of AT command you type to get responding “ok” “ok” “error” “error” and finally “ok”? It’s the same simple “AT”?
If something wrong and cause the SFU upgrade fail, the modem could stay at RECOEVR mode or FFH mode, depend on what what SFU command you used.
You could type “AT+BMOD?” to check what mode does your modem stay at. If you have UART2 console log also helpful to identify.
Usually you can re-do the SFU upgrade if SFU upgrade fail.
I’m trying to update a new device, the old device went through and was successful. unfortunately i don’t have the full logs for the update.
it appears to be just simple AT commands the screen shot shows what was being sent by the Sequans SFU software. It looks like it responded “OK” to the normal “AT” commands and there were 2 commands with “ST” that it is getting an “ERROR” responses I’m not exactly sure what these are I’m assuming trying to communicate to the chip in a few different ways to see what communication protocol it needs to use.
ill check on what mode the cell modem is in and get back to you. I’m assuming since this is a new cell modem that hasn’t started SFU it is not stuck in a different state
There are 2 devices I’m currently using one that was somehow successful(it says it is on the version i was trying to update to) when i tried SFU over UART0 there is also another new one they are both in the same operational mode and both are experiencing this device not detected when I’m using Sequans SFU
I’ve connected it to a MCU using UART0 and it is able to communicate fine, even when i use a 1.8v usb ttl i can send messages to and receive messages from the GM02SP. and then try to use that same 1.8v usb ttl and it doesnt work using Sequans SFU i see the data being sent and i see responses from the cell modem but the Sequans SFU is failing to process those messages
let me get you the exact logs for the SFU
But mainly the Sequans SFU says it is trying to detect the device using a variety of baud rates(i have also set it specifically to 115200 baud, which is what the modem is currently using as its baud rate) and after a few times doing this it gives a popup with a error saying service not detected.
I have one question, does this COM port fail detection happen in the beginning of SFU or it was successfully detected in the beginning but fail to detect again after modem reboot during SFU upgrade? I cannot tell because the log looks not the complete sfu upgrade log, it missing the beginning part.
sorry that didnt contain the full start to it, but it is never detecting the device, here are some new logs that have the start, the odd thing now is the program ends up stalling and never showing me that error message
that worked! thanks that seemed to be the main issue we are adding RST and CTS to our next board, is it better for the SFU to have hardware flow control, or is it perfectly fine to just have TX/RX exposed for UART0.
or are there any other pin(s) recommended to expose.
Good to hear it works. It’s better to have RTS/CTS & flow control. If you could add it, it will make sure there is no packet loss during fast data transfer.
RTS/CTS also have other function. I am not sure what’s your application and user cases, do you need modem to enter power saving mode to save power? RTS0 is used to wakeup modem when it enter sleep. If your application is always on and don’t need power saving, you can ignore this.
