Replies: 6 comments 1 reply
-
|
The option Try to capture the network traffic and search for the 3-way handshake (by TCP stack) for this connection - there should be a SYN-SYN-ACK sequence for the data connection (don't mix up this one with the control connection, where commands and replies are transmitted) or any hint, why the data connection could not be opened. And at the same time, you should provide a listing of the control connection - either from the automatically created log file or an extraction of the dialogs from the capture mentioned above. The "interpreter" for server responses is only a very dumb/primitive one (in my script - only the (message) numbers are checked) - any unexpected answer may (or better: will) baffle the code. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you indeed for prompt response and the hints. Please see the fraction of a Wireshark capture (with filter Packet #1457 is the last one with the |
Beta Was this translation helpful? Give feedback.
-
|
Looks like the data transmission - at least the "sending part" - was done already. You may/should count the packets transmitted or extract (from Wireshark) the payload of the FTP data connection to verify, its size is equal to the image size. At the same time the lines are looking odd - the reported memory size of 192 MB is too small regarding the installed memory of 512 MB (in all 6890 models I know) and it's further limited to 128 MB as needed by other GRX5 models (7580/7590) to preserve the memory for "bootcore" system above the uploaded image in RAM. The kernel(s) from file But with the reported memory size of 192 MB there's a chance, that the "bootcore" kernel is linked to be used from addresses above 0x8c000000 already - in this case you may call the If all hints above do not work, try it simply with an original firmware image by AVM - it seems, you've added > 5 MB to the filesystem (the original 07.29 uses only 43-44 MB) and if the size is a problem (I've no idea, why the other box should work with the same image in this case, but probably the other device reports a different memory size), you may consider a two-step approach to install the final firmware image - in the first step you've to add only your own public key used for firmware signing and afterwards you may update via AVM's GUI using your own signed file. And please ... show us/me the log file from FTP dialogs (it's YourFritz/eva_tools/eva_to_memory Line 32 in ce04c85 |
Beta Was this translation helpful? Give feedback.
-
|
Hmm ... about 1,400 packets with 1,440 bytes of data are only a fraction of data to be sent (49 MB - I've noticed the packet numbers too late) - transmission is stopped only to let the receiver process its buffers and the image isn't even halfway completely transmitted. So there are no needs to verify the size of transferred data - the other hints from above are still valid and you should process one or all (at your option). |
Beta Was this translation helpful? Give feedback.
-
Here you go: Thank you also for the other hints – much appreciated :) Will go through them one-by-one and will provide feedback. |
Beta Was this translation helpful? Give feedback.
-
From the However not sure if the warnings are relevant or not. What could be the reason for them, and might it have any impact on the issue?
This uploads indeed the entire image (which size is Unfortunately after the upload there is no FTP response with The same symptoms are when uploading with Any other ideas how to troubleshoot further? |
Beta Was this translation helpful? Give feedback.
-
|
Well, just before having some break, made yet another attempt to upload the image with Nevertheless, let me thank you very much @PeterPawn for your crucial help. I do not like to leave such unresolved problems (the root cause for the issue is still unknown). However I have to move on to the other 'faulty' 6890 and try to diagnose, why it keeps restarting every 2-3 minutes. Guess the motherboard is broken. Notwithstanding – I know this not the right thread to discuss that – if by chance anybody has any ideas, where I could start digging from, would appreciate any hints or contact @ priv. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I am trying to upload an image (based on release 07.29) to FB6890 LTE v2. However the script just hangs at the command
cat $file >$storefifoin line 172.I suspect that the issue is related to a problem with data transfer indirectly through the pipe/FIFO files and NetCat, which opens (successfully) a connection in line 172 with command
nc -w 3 $data_ip $data_port <&$upstream 2>/dev/null 1>&2 &, however for some reason there is no actual data transfer. Tried to debug and see, if the NetCat command outputs any errors by replacing the command in line 172 withnc -D -v $data_ip $data_port <&$upstream &. However the script also just hangs without any output.Tried on another, faulty FB6890 LTE v2 (it keeps rebooting every 2-3 minutes) – the image upload is successful (though the box keeps restarting).
Would appreciate any hints, what could be the reason for "hanging" the script when trying to flash the (former) FB6890 LTE v2 or how to troubleshoot that further.
Best regards.
Beta Was this translation helpful? Give feedback.
All reactions