|Subject:||Re: [Paparazzi-devel] lisa - m upload problem|
|Date:||Tue, 1 Oct 2013 23:33:16 +0300|
We did not change anything in our airframe and the other configuration files in the two trials. Then, is it possible that the generated files be different from each other? I assumed that they are exactly the same, thats why I suspect on upload process.
Just keep in mind what Michal mentioned: We don't actually know if the the generated firmware file was correct the first time... it might just as well be the case that you changed some things but didn't properly rebuild it and the actual upload was working fine...
On Tue, Oct 1, 2013 at 9:21 PM, Refik Sever <address@hidden> wrote:
It would be great to implement the CRC. I am waiting for the patches :)
It will also be OK for me to wait for the complete readback of the flash and check it on PC. Is the complete readback of flash memory from USB cable implemented? Readback from JTAG cable is another option but since the JTAG connector is in the middle, it is hard for us to connect the cable.
We added the preflight check of Manuel-Auto1-Auto2 switch to our check list. But, if the code is corrupted for different flight plan blocks, we may not detect it on the ground. That's why I want to be sure that the uploaded code is not corrupted.
CRC would be great. I actually thought there is some code checking already implemented. Although from Refiks comment it is not conclusive that the problem was a random error in the uploaded code, or the compiled code itself.
Refik, for the time being, you might want to do some extra pre-flight checks like switch to Manual-Auto1-Auto2 and look at the ap response. That would tell you if your plane is safe to fly.
On Tue, Oct 1, 2013 at 10:21 AM, Karoly Molnar <address@hidden> wrote:
Last week, we had a crash. We thought that it was due to interference from GSM base station. Today, we had another crash and we found that the two crashes were not due to interference.
We flied with the same hex file uploaded to Lisa-M. During flight in auto1, there was no problem. When we switched to auto2, the autopilot again freezed. It was exactly the same behavior with the previous crash, which also happened when we switched to auto2.
After the crash, we tested the autopilot on the ground. We send take off command in auto1, and then we manually switched to standby. When we switched to auto2, and it again freezed.
After that, we re-build the same airframe file and upload the code. Now, everything is normal. It seems that it did not upload correctly.
We are uploading the file using USB cable. Does it verify the uploaded file by reading it back? How can I make it verify the file?
Is is possible that it uploads wrong and partially runs the code? If this is the case, doesn't the MD5 signature become wrong?
_______________________________________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
|[Prev in Thread]||Current Thread||[Next in Thread]|