Teoretically, Dronekit-Python run over any hardware which supports MavLink. I tried to run dronekit over Gumstix AeroCore but I've only got reach the prompt MAV> and nothing more happens
Someone knows what's missing?
Thanks in advance
DroneKit-Python talks MAVLink indeed but it's only being tested and developed against the APM Flight Stack, if the Gumstix AeroCore runs the APM stack then there's probably no data getting to MAVProxy.
Related
I'm trying to use example code provided by X-CUBE-IAP-USART package to develop IAP FW for STM32L0xx device. I'm using STM32L073 Nucleo64 board for development.
When I send compiled FW using TeraTerm's YMODEM protocol nothing happens.
Only thing that is being send to target STM device is: "ota_test.elf166988 13332031541 100644¶Ê" over and over again. When I debugged example code I was getting HAL_TIMEOUT on receive. (rework example code to work with interrupts?). I've triple checked my USART settings so that is not the problem. Cam anyone please help me or send some functioning example code please? Original example code was written for STM32L073 eval board, but I've ported it to work with NUCLEO board, maybe I've made mistake there but, I've configured all peripherals exactly as they were configured in example code.
I appreciate any kind of help.
Thank you.
I am using STM32L476 and faced same issues while writing boodloader for my project.
The problems I encountered are:
HAL_UART_Receive() not working properly, always returning HAL_TIMEOUT
After the uart problem was solved, I was still not be able to upload bin files. Where I noticed that the codes were trying to delete the wrong memory address.
Applied solutions:
I changed the usart conection options. I used DMA channel to receive ymodem packages.
In the FLASH_If_Erase() function, pEraseInit.Banks configured 'FLASH_BANK_1' instead of 'FLASH_BANK_2'. I guess this was a bug and needs to be updated by ST developers.
I added the bootloader projects link where you can find all codes and the changes. Hope it helps with your problems.
Link : https://github.com/yelkovany/Embedded_codes.git
I've just unpacked my new Pico Pro Maker Kit and started flashing procedure. After creating a product in AndroidThings platform and downloading the build I've started flashing procedure.
Command flash-all.sh failed on fastboot syntax, so I've build that manually and found that it was failing on part "set_active _a". I've skipped that and continued to flash device.
Now device is rebooted, I can see on the screen androidThings logo and version + info about network status ("not connected").
I'm unable to find this device in
fastboot devices
or
adb devices
so it looks like I have no way to connect into it.
Do you know a way of fixing that? Is there any way to force fastboot reboot on that device?
Thanks!
I had a related problem for IMX7 on initial install, I thought I'd pass along the Boundary feedback in case it helps. Tech support at Boundary devices recommended that I try the following:
Please try to add androidboot.dm_verity=disabled and
androidboot.selinux=disabled options to bootargs.
I presume these would be options you'd set at the boot prompt ==> (from the serial connection) but I haven't had a chance to test, which I may get to next week. Interested in your feedback if this has any impact to your situation in the meantime.
I downloaded Visual Studio 2017 Community and installed it on my Windows 10 PC. I downloaded the HomeSeer templates from the VS "marketplace" and installed them. I created a new project from the C# HSPI "A" template and pressed F5 to start the debug; I get 1 error message:
Error The command "powershell -file c:\users\paul\documents\visual studio 2017\Projects\HSPIPluginA1\HSPIPluginA1\fix-output.ps1 -configuration Debug -executionpolicy Unrestricted -NonInteractive" exited with code -196608.
Project: HSPIPluginA1 File: c:\users\paul\documents\visual studio 2017\Projects\HSPIPluginA1\HSPIPluginA1\HSPIPluginA1.csproj Line: 77
Do you have any idea what I did wrong? I'm pretty bad if I can't even get the default, pre-packaged, code to work.
Also, how do I provide an alternate IP Address for the plugin to connect to? My HS3 runs on a remote Linux (Lubuntu 16.04 LTS) machine. Thanks in advance.
I did not mean to imply that I was frustrated with you - it was me I was frustrated with; there just seems to be so much to learn. I know how much time and effort it takes to create/package/edit/document things so other folks can use them, so I certainly don't want to be a "whiner" right at the start. I also really appreciate you made the modifications to the template so quickly.
Thanks for reporting.
I just published an update to the extension that corrects the problem you were having. The corresponding tracking issue is https://github.com/alexdresko/HSPI/issues/62
I haven't finished the documentation yet, but you can see how to change the IP and port by going to https://github.com/alexdresko/HSPI/issues/7#issuecomment-283101463
Please do not expect perfection from this project. It's something I'm working on in my spare time and I am in no way affiliated with HomeSeer.
Now that I think about it, I do not know if this project will work with Linux, as that is something I haven't tested yet. I am very interested to know if it works, so please keep me updated.
Thanks again!
I am a beginner to DBus and wrote one sample application using dbus but i am facing a weird problem. My app is running fine on guest os as Ubuntu (On virtual box with windows host ) but the same app is not working on standalone Ubuntu system (also tried on meego, no luck thr as well).
Then, i verified the obvious doubts on dbus, glib libraries versions. Its same on both the environments, and the issue is consistent. I mean the app always runs without any prob on virtual box and always crashes on the standalone ubuntu.
Here is the brief desc about the issue.
App is supposed to send 150 signals on dbus and another app is
receiving these signals. (No issues here in send & receive).
I have an array of DbusMessage[150] (also tried with the list of 150 DBusMessage)...appending the arguments on to the dbus msg and sending on to bus..one at a time...no looping...
The sequence of dbus APIs are all correct and verified by referencing multiple sample source code.
All of above works fine, but on the standalone ubuntu system, i can always see segmentation fault, on dbus_connection_send() call.
I reverified everypossible places where in "seg faults" can happen and it all looks fine to me. This is how i am appending my arg to dbus message.
dbus_message_append_args(pDbusMsg, DBUS_TYPE_ARRAY, DBUS_TYPE_BYTE, &pData, sizeof(pData),
DBUS_TYPE_INVALID) != TRUE)
then connection send..and then calling dbus_connection_flush(). Also as my app has to send the same message again (but not immediately), i am re registering the same signal by calling dbus_message_new_signal()..i have verified all the pointers / memory / dbusmessage..everything looks fine and works fine on virtualized ubuntu os.
Just to add, i tried sending with dbus_connection_send_preallocated() and it works fine for few messages(10-15~), but not consistent enough.
Have you ever had this kind of issue, please let me know any clue to solve this prob....Any help would be appreciated or any examples/tutorials as well taking into consideration I'm just starting out with dbus :P
Thanks
I dont know if you have heard about dbus related debugging tools. For beginning you can try calling the exposed functions using some dbus-debugging-tool. If it doesnt throw segmentation fault when you call using the tool, then probably you should look for issues in your code. Otherwise you should check things related to environment.
One such tool is - DFeet
Another such debugger(commandline based) is provided by Qt people as well.
First of all a statement: I'm a newbie when it comes to programming for the Mac. However I have an assignment which requires USB communication with a device so I thought I'll start with something basic.
I took the code from here, built it and ran it from the Terminal. It starts up and writes:
Looking for devices matching vendor ID=1351 and product ID=8193.
Starting run loop.
However after this, if I plug in and out USB devices (I tried: iPod, GPS, mouse) nothing gets written on the screen, although as much as I understand there should be whenever I connect and disconnect a device.
What am I doing wrong?
Thanks in advance.
You can also use system_profiler SPUSBDataType on a terminal
I found /Developer/Applications/Utilities/USB Prober to be of great use.