Re: [Paparazzi-devel] Black Magic Probe: Why two ttyACM* devices?

[Michal Podhradsky]

True, I was just curious.

So if I use
<subsystem name="telemetry" type="transparent"/>

  <configure name="MODEM_PORT" value="UART3"/>

</subsystem>

then somehow the BMP serial gets mapped to UART3?

On Mon, Mar 30, 2015 at 2:13 PM, Felix Ruess <address@hidden> wrote:

From the AP code you just use the normal uart.

Or you can directly use <subsystem name="telemetry" type="transparent_usb"/> to send it over usb directly and then not use the BMP (or any other serial->usb converter).

On Mon, Mar 30, 2015 at 11:00 PM, Michal Podhradsky <address@hidden> wrote:

Stupid (but related) question - how do I access the BMP serial port from the AP code? For example, can the telemetry be sent over that UART-BMP port?

On Mon, Mar 30, 2015 at 12:23 PM, Felix Ruess <address@hidden> wrote:

I always add the bmp to my udev rules to create some nicer symlinks:

SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic GDB Server", SYMLINK+="bmp-gdb"
SUBSYSTEM=="tty", ATTRS{interface}=="Black Magic UART Port", SYMLINK+="bmp-serial"

then I can use /dev/bmp-gdb for flashing and debugging and /dev/bmp-serial for the - well - serial...

On Mon, Mar 30, 2015 at 9:02 PM, Simon Liebold <address@hidden> wrote:

Michal, Felix, thanks. That did help.

I preconfigured it into my airframe file, so that I can use the "Default" flash mode:

<firmware name="rotocraft">
    ...
    <configure name="FLASH_MODE" value="SWD"/>
    <configure name="BMP_PORT" value="/dev/serial/by-id/usb-Black_Sphere_Technologies_Black_Magic_Probe_E3C1A9DD-if00"/>
</firmware>

(Not sure if the serial E3C1A9DD from above example will work for everyone.)


Waiting for the storms to calm down to do more test flying:
Simon

Am 30.03.2015 um 18:57 schrieb Felix Ruess:

The second /dev/ttyACMx is a serial device connected to the UART port on the back of the BMP.

So that is basically just like a FTDI serial<->USB adapter and you can use it to e.g. connect to the telemetry uart port on the ap for desk testing.

On Mon, Mar 30, 2015 at 6:51 PM, Michal Podhradsky <address@hidden> wrote:

Simon, you have to use swdp_scan instead of jtag_scan for Lisa MX / F4, see wiki: http://wiki.paparazziuav.org/wiki/RT_Paparazzi

I dont know why there are two devices, but you always want to use the first one (i.e. a lower number one).

M

On Sat, Mar 28, 2015 at 4:03 PM, Simon Liebold <address@hidden> wrote:

So far I only used the BMP to upload the firmware onto my Lisa MX using
SWD on latest master. The JTAG option never worked for me (with the
"JTAG device scan failed!" error). I never used the BMP for any
debugging - nor would I know how to do that.

But why does it create two ttyACM* devices when plugging in? Is the
other one supposed to work with the JTAG upload setting? I read that
flashing via JTAG would be much faster than via SWD. Is that correct?

Simon


_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel