Re: [Paparazzi-devel] Can I replace Floss-JTAG by JLINK-V8 produced by SEGGER

[刘]

Thanks a lot for your gelivable reply. 

There are several new questions:

1.  Is the sentence <configure name="ap.OOCD_BOARD" value="jlink"/> should be add in file **.xml? As there are some many .xml, I don't know which one is the one that I needed.

2. As you suggested, we have successfully uploaded the bootloader via some means. However, we meet new problem now

Look forward for your reply .

Sincere Lexy

At 2014-10-08 16:53:12, "Felix Ruess" <address@hidden> wrote:

Hi,

you can of course always use your own tool to upload the final firmware hex/elf file from var/aircrafts/<name>/ap/ap.hex

If the Segger-JLINK works with OpenOCD you can probably just <configure name="ap.OOCD_BOARD" value="jlink"/> or something like that.

Cheers, Felix

On Mon, Sep 29, 2014 at 10:40 AM, Lexy_ac <address@hidden> wrote:

Dear Sir or Madam:

Please turn to this link first→ http://wiki.paparazziuav.org/wiki/Luftboot

During the procedure “Uploading the luftboot USB bootloader”, Floss-JTAG and
Blacksphere mini JTAG are verified to be employed. Unfortunately, we have
tried our best to find the  proposed two, but we failed. Now, we just have a
Segger-JLINK V8 . Can we replace the proposed two by the Segger-JLINK?If
can, how?

Thanks a lot.



--
View this message in context: http://lists.paparazziuav.org/Can-I-replace-Floss-JTAG-by-JLINK-V8-produced-by-SEGGER-tp16191.html
Sent from the paparazzi-devel mailing list archive at Nabble.com.

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