These are chat archives for PX4/Hardware

29th
Dec 2015
Mark Whitehorn
@kd0aij
Dec 29 2015 00:57
parameters loaded immediately running mavproxy on Ubuntu 14.04, so there seems to be a USB problem on 15.10
But set <param> value still times out.
Also, SYS_AUTOSTART displays as 0.0 even though it has integer value 4009
Lorenz Meier
@LorenzMeier
Dec 29 2015 13:53
@nickarsov Is your bootloader issue persisting?
Phillip Kocmoud
@pkocmoud
Dec 29 2015 13:55
Yes
Nick just sent a request via email.
Lorenz Meier
@LorenzMeier
Dec 29 2015 13:57
Can you just flash via a Linux box from the shell?
Nick Arsov
@nickarsov
Dec 29 2015 14:02
Hi guys. I can flash using just ST-Link utility, but need *.bin file instead
or hex file
Phillip Kocmoud
@pkocmoud
Dec 29 2015 14:02
Nick, you are Windows only, correct?
Lorenz Meier
@LorenzMeier
Dec 29 2015 14:02
No, I meant flashing the Firmware
Nick Arsov
@nickarsov
Dec 29 2015 14:03
yes, I can flash it via ST-Link. Yes, just Windows 7/32
but ST-Link uses only bin or hex files
Phillip Kocmoud
@pkocmoud
Dec 29 2015 14:04
You would have to flash the application to an offset address.
Nick Arsov
@nickarsov
Dec 29 2015 14:05
yes, sure....can someone tell me the offset?
Phillip Kocmoud
@pkocmoud
Dec 29 2015 14:18
Nick you have 2 issues, someone would need to extract the bin from the .PX4 and also the provide the offset.
Lorenz Meier
@LorenzMeier
Dec 29 2015 14:28
I can flash fine
Screen Shot 2015-12-29 at 15.27.50.png
Using this daily build QGC version
Phillip Kocmoud
@pkocmoud
Dec 29 2015 14:29
This issue is specific to the new PixRacer boards. The beta board still works fine for Nick.
Wonder if it is the Baro SPI bus switch?
Lorenz Meier
@LorenzMeier
Dec 29 2015 14:31
That should not influence the bootloader
Were there any USB related changes?
Phillip Kocmoud
@pkocmoud
Dec 29 2015 14:32
I have asked for guidance. The older bootloader not longer works.
Lorenz Meier
@LorenzMeier
Dec 29 2015 14:33
You really need to flash the board using the proper development tools
The workflow of trying to bring up new boards using customer / consumer tools is just wrong
Phillip Kocmoud
@pkocmoud
Dec 29 2015 14:34
Unfortunately that is the only feedback so far. We will need to wait then.
Lorenz Meier
@LorenzMeier
Dec 29 2015 14:35
I can’t see how moving the baro would induce any sort of bootloader related change. Nick needs to go back to the schematic and ensure that there are no power or USB related changes
Mark Whitehorn
@kd0aij
Dec 29 2015 18:36
Some more observations of USB behavior differences between X2 and PixRacer:
PixRacer issues nsh prompt on /dev/ttyACM0 at boot when connected to a USB3 port. No printout at boot when connected to a USB2 port, and no response to Enter key.
X2 prints nothing on /dev/ttyACM0 when connected to either USB2 or USB3 ports, but responds to Enter key with nsh prompt.
mavproxy connects properly to both PixRacer and X2 after first invoking rc.usb using serial terminal