Build Firmware on windows or Linux

wswday · January 17, 2016, 9:32am

I build Firmware on windows using make px4-stm32f4discovery_default (spend 6 hours). It can work on stm32f4discovery board.
but if I build on ubuntu ,It can’n work (can’n Connect to the NuttX Terminal via UART2).
Why it spend 6 hours when i bilud on windows?
Why it can’n work when i build on ubuntu?
Somebody help me please.

LorenzMeier · January 17, 2016, 11:16am

Use the build instructions on http://dev.px4.io. And make sure to follow every step. It will work all fine then.

It would also have told you that you shouldn’t use Windows.

wswday · January 17, 2016, 11:50am

I have try many times step by step. It can’t work , although i have installed Snapdragon Flight‘s toolchain.I don’t know if because i use ubuntu14.04 .

LorenzMeier · January 17, 2016, 1:02pm

You are not building for a Snapdragon Flight if you want to run on the STM32F4 discovery. That is a NuttX board. I just build the target locally without issues, so something is wrong with your setup.

wswday · January 17, 2016, 1:06pm

I can build target without issues,but when i upload to STM32F4_discovery , it can’t work(can’n Connect to the NuttX Terminal via UART2).

LorenzMeier · January 17, 2016, 1:32pm

You need to check if you configured and wired everything correctly. Can you connect to the terminal via USB?

wswday · January 17, 2016, 1:41pm

i sure i wired everything correctly,because i have try build using windows and upload to the board.And everything is ok. I can connect to the terminal via usart2, but can’t via usb.
But if i build using ubuntu ,it can’t work . can’t via usart2 nor usb.

JulianOes · January 18, 2016, 3:55pm

So what you’re saying is that you can’t connect to either USART2 or USB on Linux?

If yes, what is the command you are trying? Can screen open the port but you don’t get the nsh console or can you not even open the port?

FreelyHard · January 18, 2016, 5:08pm

About the question of windows build, maybe your computer is i7 type U, or It’s the feature about windows. You can use the windows task manager, in the process column , right click, and change the task priority to high. It makes effect significantly.

abhijit_dasgupta · January 22, 2016, 3:37pm

hi, I have followed the way it was mentioned in “http://dev.px4.io/” for windows. But, in one sometime the build is created successfully but in sometime it shows an error underfine reference “get_errno_ptr”. but the behavior of the error is not predictable. in sometimes it shows in at the copletion of building 8% and sometime 20%. Any help is appreciated.

Thanks.

LorenzMeier · February 13, 2016, 10:02pm

The documentation says that Windows is not supported. Please use an Ubuntu VM or dual-boot.

kno · March 31, 2016, 5:40pm

Hello,

I am also experiencing this issue of no connectivity when trying to access the PX4 nsh over UART on the Discovery board. I’m on the latest stable branch, no build or programming errors.

I verified my wiring by flashing stock NuttX to the board, and was able to access nsh over both USB and UART2 w/ FTDI cable no problem. Switching back to the PX4 discovery bootloader + px4-stm32f4discovery_default build, I get nothing on either port.

Any assistance would be greatly appreciated.

edit: I am on Ubuntu 14.04 using arm-none-eabi-gcc version 4.8.4

LorenzMeier · April 1, 2016, 6:56am

The discovery board is an experimental target not within the main line of support. It will likely take some debugging effort. Officially maintained boards are listed under autopilots on http://dev.px4.io

c3po · April 6, 2016, 7:45pm

I am currently having the same problem with the stm32f4discovery. Compiling and uploading works well, but I am not able to get the nsh terminal to work. After compiling with the CONFIG_DEBUG flag set in nuttx-configs/px4-stm32f4discovery/nsh/defconfig, I get the following output on the UART connection that I set up for connecting to nsh on USART2 on the discovery board:
Airq_unexpected_isr: irq: 2 Assertion failed at file:irq_unexpectedisr.c line: 86 task:
where it seems like the first character (‘A’), is from the showprogress() function being called in stm32_start.c on line 208. And since no ‘B’ shows up in the terminal, it seems like this is about as far the initialization gets in my case.

Will continue debugging, but hope this can be helpful to those of you that are having the same problem.

My setup: Xubuntu 14.04 with arm-none-eabi-gcc 4.8.4

skye-AL · May 16, 2016, 7:25pm

I experienced the exact same problem (compiling and uploading works, but no nsh terminal), any solution so far?

clovett · June 14, 2016, 8:46pm

I have nsh working with STM32Discovery board (on Windows). I’m following these directions, https://pixhawk.org/modules/stm32f4discovery but I was able to connect the USART2 pins directly to my PC using a FTDI serial USB cable (like this one https://www.sparkfun.com/products/9717) and Putty connects to the board and nsh is good.

ReedNoel · August 7, 2017, 3:23pm

The 1st time a trying build fw px4, so happend error, please help

ReedNoel · August 19, 2017, 2:27am

I trying to build firmware px4-stm32f4discovery but I can’t, who 's already build it, please give me with many thanks.
Reed.

ReedNoel · August 19, 2017, 4:08am

Hi guys,
Please help. I lost 2 days, but can’t build fw STM32F4 Discovery, Who had it please send to me,
Rgs
Reed