Error Building Pixhawk in External mode
1 visualización (últimos 30 días)
Mostrar comentarios más antiguos
Help,I can't build on Matlab with PX4:
>> PixhawkPSP('/usr/local/MATLAB/px4')
Found compatible version R2017b Using Target Package path of /usr/local/MATLAB/px4
Error using sprintf Function is not defined for 'cell' inputs.
Error in codertarget.pixhawk.Px4PSP_Install_UI/build_firmware_callback
Error using matlab.ui.control.internal.controller.ComponentController/executeUserCallback (line 309) Error while evaluating Button PrivateButtonPushedFcn.
Operation terminated by user during PixhawkPSP (line 82)

2 comentarios
Steve Kuznicki
el 14 de Dic. de 2018
We are looking into this and will provide a workaround/solution.
Steve Kuznicki
el 14 de Dic. de 2018
By the way - you don't need to "build" the firmware using this UI. I would suggest using the UI for downloading the firmware, then exit the UI. Then using a terminal window, go to the "Firmware" folder and issue a "make px4fmu-v2_default" (or whatever target you have). If you can build the firmware using this method, then you should be good to go using a Simulink model and "build".
Respuestas (1)
Erlantz Otaola
el 3 de Dic. de 2018
The same problem here. I haven't found a solution yet.
2 comentarios
Erlantz Otaola
el 13 de Dic. de 2018
We did eventually notice that we were using a gcc-7 compiler. The right way to do it is using the gcc-5.4 compiler, which solves that error.
N/A
el 25 de En. de 2019
Can you elaborate on the settings you set in Simulink, to get the ext_mode_intro.slx example working? For example, what settings need to be set in Simulation > Model Configuration Parameters > Hardware Board settings > Target hardware resources > External mode options?
I currently have
"Data Exchange Serial Port" = ttyACM0 (Ubuntu 18.04, Matlab 2017b, and since I use the USB cable directly, no FTDI)
"Baud Rate Select" = 115200
Furthermore, under Model Configuration Parameters > External mode configuration, I have:
"Transport layer" = serial . Mex-file name: ext_serial_win32_comm (unable to change that fromhere)
"MEX-file arguments" = 1 8 115200 5
I suspect that there is some discrepancy in defining these arguments, involving COM ports in Linux.
Any tips or suggestions are welcome!
Ver también
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!