![]() Building CXX object msg/CMakeFiles/uorb_msgs.dir/topics_sources/adc_report.cpp. Building CXX object msg/CMakeFiles/uorb_msgs.dir/topics_sources/actuator_ ![]() Building CXX object msg/CMakeFiles/uorb_msgs.dir/topics_sources/ Scanning dependencies of target uorb_msgs Linking CXX static library libtinybson.a Building CXX object src/lib/parameters/tinybson/CMakeFiles/tinybson.dir/ Scanning dependencies of target uorb_headers VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “make “” in directory “c:\PX4\home\Firmware\VisualGDB\Debug” on local computer = Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped = Stop.ĭirectory: c:\PX4\home\Firmware\VisualGDB\Debug Make: *** No targets specified and no makefile found. ![]() VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe –login -c “make “” in directory “c:\PX4\home\Firmware\VisualGDB\Debug” on local computer Build started: Project: Px4_WinGDB, Configuration: Debug VisualGDB. ![]() Here is the output of the latest VisualGDB: I tested again with version VisualGDB-5., the command line looks same, but without –login, and make process is working (until it stops on because of login problem). Now i can see the login command, but something strange happens. VisualGDB: Error: Command-line action failed G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″ĭirectory: /cygdrive/c/PX4/home/Firmware/VisualGDB/Debug usr/bin/bash: C:PX4toolchaincygwin64bincmake.exe: command not foundĮxecutable: C:\PX4\toolchain\cygwin64\bin\bash.exeĪrguments: -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe. G \”Unix Makefiles\” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_COLOR_MAKEFILE=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DTOOLCHAIN_ROOT=C:/PX4/toolchain/cygwin64″” in directory “/cygdrive/c/PX4/home/Firmware/VisualGDB/Debug” on local computer VisualGDB: Run “C:\PX4\toolchain\cygwin64\bin\bash.exe -c “C:\PX4\toolchain\cygwin64\bin\cmake.exe. Build started: Project: Px4_WinGDB.vgdbcmake (failed), Configuration: Debug VisualGDB - Enter the following command in the console: pip3 install -user kconfiglib jsonschema future Getting Started The toolchain uses a specially configured console window (started by running the run-console. On rebuild command i got following message: System.Exception: CMake exited with code 34304 System.Exception: Unexpected JSON message: expected Reply, got Unexpected JSON message: expected Reply, got On the build command i get following message:Īssertion “0” failed: file “/home/salex/CMake/Utilities/cmlibuv/src/unix/core.c”, line 185, function: uv_closeġ cmake 47776 cygwin_exception::open_stackdumpfile: Dumping stack trace to The problem you mentioned happens every time i try to build the project. If there are no issues, at the end of flash process, the module will be reset and “hello_world” application will be running there.I succeeded to load the project without errors. Wrote 22992 bytes (13019 compressed) at 0x00001000 in 0.3 seconds (effective 558.9 kbit/s). 4.3 Pixhawk Toolchain MathWorks PSP Install (Linux/Windows). Running esptool.py in directory /esp/hello_worldĮxecuting "python /esp-idf/components/esptool_py/esptool/esptool.py -b 460800 write_flash -b 460800 write_flash -flash_mode dio -flash_size detect -flash_freq 40m 0x1000 bootloader/bootloader.bin 0x8000 partition_table/partition-table.bin 0x10000 hello-world.bin
0 Comments
Leave a Reply. |