soycamo - Thank you for the comments.
"We were using this part for the Maple Bacon: STF202"
That is the chip Siy uses for USB termination and ESD protection. AFAIK, based on a post be feurig, that is where Maple bacon took that part of its schematic.
For me, the NUF2042XV6 has a few advantages over the STF202.
To make my boards easier to make, I try to restrict them to SMD on one side only. I like this approach a lot (we used it on the OU's SenseBoard, but not fully). This makes DIY SMD simpler. For example, it lets folks use the SMD reflow 'skillet' technique. To make the USB socket connection more robust the USB socket is thru-hole. To get more space for SMD, and more space for user silk screen, the USB socket in on the non-SMD side, along with all of the users silk screen. So thru-hole USB sockets are my favoured approach.
The pinout of the NUF2042XV6 is easy to route to the thru-hole USB socket. The STF202 seems a better fit with SMD USB sockets.
Before doing the mini, I had been playing with a design for a 64pin LQFP STM32F103/STM32F4 board. STM32F2 and STM32F4 have USB pull-up resistors built into the chips full-speed USB peripheral, so I thought they could skip external pull-up resistor circuitry. Hence the NUF2042XV6 seems ideal; the pull-up parts can be omitted for STM32F4, and it should work correctly. However, it is more messy to use the STF202 with STM32F4; either the Vusb input signal can't be connected, and hence Vusb can't be ESD protected, or the on-board R-up mustn't be used. I was trying to minimise hacking on the USB libraries, which I assumed used the on-board R-up (I didn't check) so I chose to use the NUF2042XV6. AFAIK, the only 48pin STM32F4 is the STM32F401, and I haven't even looked to see if it would be easy to modify Orone-mini for it, so it isn't yet an import consideration.
There are a few other USB termination and ESD parts. For example the Semtech EClamp2522P looks perfect, though it is still 1.6mm x 1.6mm. The USB R-up is controlled by a separate pin, and isn't wired directly to Vusb. Unfortunately, the ground connection is a pad under the chip. I am not confident that a newbie (or me) could make that using simple SMD techniques, and I think it'd be awkward to diagnose the defect and fix it. I might change my view if SMD solder paste templates are easy to make.
"One thing that has bothered me that I wanted to fix on my own board is the USB-connected pins. After @feurig gave a class on using the Maple, a student came by a local gathering to explain that he thought he had bricked his Maple Bacon, only for @feurig to discover that it was because of using the pins connected to USB."
Yes that is a serious concern that I share.
"Soooo we should ax those. However, I'd like to hear arguments on keeping the pins around (or maybe making those pins be optional somehow?"
I don't want to remove the USB D+ or D- signals from the pin header because:
1. the Orone-mini is no longer Maple-mini compatible (on the pin-outs they share)
2. If the Orone-mini is used in a design which doesn't use USB, then those two pins can be used as normal I/O. It seems a shame to waste them. It seems like removing those pins penalises the smart to protect the ignorant (or worse), which is not a principle I like to encourage. I would hope the person who made the mistake learned something quite valuable, and that's one of the aims. My 64pin designs don't put USB D+/D- signals on header pins because I/O seems less precious than on the mini, and I am trying to cram into a limited number of pins.
To reduce the problem of the USB pins being used by accident, I am planning changes to the silk screen. The silk screen still needs improving anyway (ADC, PWM), so warning that two pins are USB seems to be a good improvement.
Anyone have an Eagle library part for a 'skull and crossbones" or a "Warning" sign?
I could put solder bridges in the USB D+/D- tracks so that the header pins are normally not connected. However, it is a small board and I'm trying to keep the ground plane as big as practical. Also I believe the USB signals should be simple and direct, with no 'stubs', and bridges with 'optional' tracks would create 'stubs'. So I am less enthusiastic about that than leaving those as they are. I am still open to persuasion.