From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: Samuel Martin <s.martin49@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v2 2/2] package/picotool: new package
Date: Fri, 12 Jul 2024 15:28:10 +0200 [thread overview]
Message-ID: <20240712152810.4a4f12f3@windsurf> (raw)
In-Reply-To: <20240228202414.719244-2-buildroot@bubu1.eu>
Hello Marcus,
On Wed, 28 Feb 2024 21:24:13 +0100
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:
> +config BR2_PACKAGE_PICOTOOL
> + bool "picotool"
> + depends on BR2_INSTALL_LIBSTDCPP
> + depends on BR2_HOST_GCC_AT_LEAST_4_9 # libusb
> + select BR2_PACKAGE_LIBUSB
> + select BR2_PACKAGE_PICO_SDK
> + help
> + picotool is a tool for inspecting rp2040 binaries and
> + interacting with rp2040 devices when they are in bootsel
> + mode or devices USBstdio support from the Raspberry Pi Pico
> + SDK.
> +
> + https://github.com/raspberrypi/picotool
Could you give some details on the use case for having picotool on your
target? In which context is your RP2040 connected to your target
system generated by Buildroot?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-12 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 20:24 [Buildroot] [PATCH v2 1/2] package/pico-sdk: new package Marcus Hoffmann via buildroot
2024-02-28 20:24 ` [Buildroot] [PATCH v2 2/2] package/picotool: " Marcus Hoffmann via buildroot
2024-07-12 13:28 ` Thomas Petazzoni via buildroot [this message]
2024-07-15 18:31 ` Marcus Hoffmann via buildroot
2024-07-15 19:45 ` Thomas Petazzoni via buildroot
2024-07-15 19:44 ` [Buildroot] [PATCH v2 1/2] package/pico-sdk: " Thomas Petazzoni via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240712152810.4a4f12f3@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@bubu1.eu \
--cc=s.martin49@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox