Path: ...!2.eu.feeder.erje.net!feeder.erje.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: F2FS On USB Sticks?
Date: 30 Mar 2025 00:31:45 GMT
Lines: 75
Message-ID: <m4rhngFdkg1U1@mid.individual.net>
References: <vrikv7$icpd$1@dont-email.me> <sm0v7s2spt5.fsf@lakka.kapsi.fi>
	<lYednSXFeZiM00D6nZ2dnZfqnPudnZ2d@giganews.com>
	<g520blxb3v.ln2@Telcontar.valinor> <vrkdlc$257qv$3@dont-email.me>
	<m46f8sFcqfqU2@mid.individual.net> <vrmebq$1sbl$2@dont-email.me>
	<m48g7uFme0qU3@mid.individual.net> <vrnlvh$1499t$2@dont-email.me>
	<09GcnUsbvK9iQUL6nZ2dnZfqnPWdnZ2d@giganews.com>
	<vrrfpm$pe22$1@dont-email.me>
	<orqdnY6y-r5foX_6nZ2dnZfqn_idnZ2d@giganews.com>
	<vru34q$35tnk$2@dont-email.me>
	<CI-cnQeLwsO_P3_6nZ2dnZfqnPidnZ2d@giganews.com>
	<vrue2m$3gbfr$1@dont-email.me> <sm0y0wqq08n.fsf@lakka.kapsi.fi>
	<a96cndfwF5EN6Xr6nZ2dnZfqn_qdnZ2d@giganews.com>
	<vs8tgq$1f267$2@dont-email.me> <m4qoeoF9vuuU1@mid.individual.net>
	<vs9jf6$25828$3@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net DlD4d2RC6j18YJWwhLIDmgLkMkCI/+hpkr+ZvmNC5oy8qhjA3s
Cancel-Lock: sha1:rUTYB+C0a6XkGvVRmAdUR/cy00I= sha256:4ZzQpuM73odSbiat1uLJe7xz/f5+wN+g07VuVaeG368=
User-Agent: Pan/0.160 (Toresk; )
Bytes: 4114

On Sat, 29 Mar 2025 19:59:34 +0000, The Natural Philosopher wrote:

> On 29/03/2025 17:20, rbowman wrote:
>> On Sat, 29 Mar 2025 13:44:58 +0000, The Natural Philosopher wrote:
>> 
>>> On 29/03/2025 04:18, c186282 wrote:
>>>> For today's uses, esp for newbies, the Pico is likely
>>>>     one of your best choices.
>>> Getting the SDK installed and working is non trivial. Getting Cmake to
>>> do what's wanted is non trivial...
>> 
>> "Getting started with Raspberry Pi Pico-series"
>> 
>> https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf
>> 
>> If you can't follow that you probably shouldn't be messing with a Pico
>> without adult supervision.
>> 
> You may follow it., bit it doesn't always work...

I'm certain people can figure out how to fuck it up.

> 
>> 1. Install VS Code 2. Install the Raspberry Pi Pico VS Code Extension
>> 3. Compile and run 'blink'
>> 
>> "The extension will now download the SDK and the toolchain, install
>> them locally, and generate the new project. The first project may take
>> 5-10 minutes to install the toolchain. VS Code will ask you whether you
>> trust the authors because we’ve automatically generated the .vscode
>> directory for you. Select yes."
>> 
>> On some Linux distros you may have to install python, git, tar, and
>> build-
>> essentials.
>> 
> And cmake ...

To repeat:

"The first project may take >> 5-10 minutes to install the toolchain."

The toolchain includes cmake. 

> Have you actually done this yourself?

Yes, most recently with the Pico2 W I got last week.  The Raspberry Pi 
Pico extension allows you to specify the board and correctly handles the 
Pico W and Pico 2 W boards. 

// Pico W devices use a GPIO on the WIFI chip for the LED,
// so when building for Pico W, CYW43_WL_GPIO_LED_PIN will be defined
#ifdef CYW43_WL_GPIO_LED_PIN
#include "pico/cyw43_arch.h"
#endif

Because the onboard LED is integrated with the WiFi chip the procedure is 
more complicated than the the non-W blink.

And before you ask, I have also used CircuitPython, MicroPython, and the 
Arduino framework with the Pico to compare them. For a Python solution I 
prefer MicroPython since it handles interrupts and _utilizing the second 
core. I have not yet tried the RISC-V core in the Pico 2. MicroPython also 
has a decorator that allows for inline PIO programming that I do not 
believe CircuitPython has. 

The Arduino core approach allows using the C/C++ structure familiar to 
many people but I'm sure at some point if you need to get down into the 
weeds to do bit-twiddling in the registers you would need to use the RPi 
C/C++ SDK.