#tinyusb
fallow birchBOT
fallow birchBOT
fallow birchBOT
rose wedge
Is there a list showing which esp-idf version works with which tinyusb version
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
Latest testing with completely unchanged firmware was seemingly successful. I changed the debugger!
- Previously: Segger J-Link BASE (using Segger GDB server)
- Now: ST-Link V3 with openocd
I can even start up the device in 96 kHz mode
But it fails during use, at dcd_dwc2.c:658, which seems to be expected.
if(dir == TUSB_DIR_OUT)
{
// Calculate req...
fallow birchBOT
fallow birchBOT
I feel you, I don't buy expensive kit myself as well. I have ordered an G0B1 nucleo (waiting for delivery), but look like it only has 1 usb for stlink. I checked that D+/D- is routed out to header, I have a few Adafruit usb breakout cable so hopefully it will work https://www.adafruit.com/product/4448
fallow birchBOT
FIFO based R/W functions dcd_read_packet_memory_ff() and dcd_write_packet_memory_ff() need to be modified for 32bit alignment.
Both linear & wrapped parts of the circular fifo need to be read/write from/to the packet buffer.
In 16bit case linear part can only be odd or even so it's easy to handle.
Now linear part can remain 0-3 bytes after last 32bit aligned transfer...
fallow birchBOT
fallow birchBOT
Describe the PR
Fix #1658 bit field ordering normally start from 0 for first field
fallow birchBOT
will revise other mcu and make an PR to fix this, btw, I have ordered a few more wch boards, they seem to look good on specs. Though to be honest, I am not familliar with wch family.
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
@hathach The build pre-comit is failing. I do not understand why file
FreeRTOS_Kernel_import.cmakerequires a blank line at the end of the file. The filepico_sdk_import.cmakedoes not have one.
You need to leave an empty line at the end of the file to make ci check happy. On my editor the pico_sdk_import.cmake does have one.
fallow birchBOT
fallow birchBOT
The attached image is from DOS and Windows. MacOS didn't display any CFG_TUSB_DEBUG=3 message when sending a break as such:
import serial
s=serial.Serial('/dev/ttyACM1')
s.sendBreak(100)
vocal harness
does tinyusb work on a raspberry pi 4?
fallow birchBOT
vocal harness
managed to fix that by symlinking aarch64-none-elf-gcc to gcc, now i'm getting
CC board.o
CC main.o
CC msc_disk.o
CC usb_descriptors.o
CC tusb.o
CC tusb_fifo.o
CC usbd.o
CC usbd_control.o
CC audio_device.o
CC cdc_device.o
CC dfu_device.o
CC dfu_rt_device.o
CC hid_device.o
CC midi_device.o
CC msc_device.o
CC ecm_rndis_device.o
CC ncm_device.o
CC usbtmc_device.o
CC video_device.o
CC vendor_device.o
LINK _build/raspberrypi_cm4/cdc_msc.elf
/usr/bin/ld: cannot find -lnosys
collect2: error: ld returned 1 exit status
make: *** [../../rules.mk:172: _build/raspberrypi_cm4/cdc_msc.elf] Error 1
robust walrus
does tinyusb work on a raspberry pi 4?
Trying to use it bare metal? It did a while ago but I haven't used it recently. (CircuitPython bare metal uses it)
vocal harness
Trying to use it bare metal? It did a while ago but I haven't used it recently. ...
i'm pretty new to this. i saw your video. there is a project that emulates the portal of power for skylanders using a pico, i was hoping to port the functionality to a pi 4 with a touch screen and make it a little more kid friendly
robust walrus
I don't know what the skylanders thing does but you likely don't need a pi 4 to change how it works
vocal harness
i know i don't need a pi for it's base functionality. this is the base project: https://github.com/NicoAICP/KAOS
instead of using the lcd/buttons, i want to make a touch screen interface for it
robust walrus
instead of using the lcd/buttons, i want to make a touch screen interface for it
Something like https://www.adafruit.com/product/2050 would allow you to do that with a pico
fallow birchBOT
vocal harness
I'm looking to be able to click and swipe. Similar to behavior my son already knows from his tablet. I really don't think the Pico is going to have the power for everything I want to do. At least not be able to do it smoothly.
There are a couple of different character types. I want to be able to have a smooth graphical interface for displaying their categories. When he clicks on an icon for a category, I want them to be able to swipe up and down between the characters available in that category. There will also be a back button to go back to the category selection screen.
My first thought was to just use the Pico and connect to it over a serial connection to give a commands. Then I read the pi 4 can act as a USB device and that seemed like the easier path. It's starting to feel like my over engineered serial communication will be easier
robust walrus
you might be surprised how fast the pico is
vocal harness
I did look into it. I was also looking at another chip I can't remember what it was that was slightly more powerful. Still not enough to do everything I want to.
fallow birchBOT
@hathach The change @mikee47 submitted is correct per the MIDI Class spec. 0x8 is Note Off. 0x9 is Note On. I pasted the table from the USB spec for your convenience.
fallow birchBOT
@hathach The change @mikee47 submitted is correct per the MIDI Class spec. 0x8 is Note Off. 0x9 is Note On. I pasted the table from the USB spec for your convenience.
thank you, I am actually planning to review your midi host, but couldn't manage the time. I gues we could merge this quick fix first.
fallow birchBOT
slow hinge
Does pio usb on the pico work as a pass through? Mitm kind of thing and is there any examples that do this?
robust walrus
Does pio usb on the pico work as a pass through? Mitm kind of thing and is there...
I know there is an Arduino library for it. I imagine there are plain C examples too
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
Implemntation __builtin_ctz(x) for IAR , see issue #2060
Describe the PR
eliminate all the warnings for IAR host portable module for the Renesas RA family.
Additional context
Please see the table describing the __packed macro. This should work for ARM and RX families on IAR.
I only tested this on RA4M2 and RA4M3
fallow birchBOT
fallow birchBOT
fallow birchBOT
How about make the cache related function optional (default ON) ?
For IMX.RT in order to have best performance, RAM will be configured to ITCM & DTCM, so they are accessed at CPU clock instead of bus clock (600MHz vs 133MHz)
Since TCM bypass the cache there is no need to flush or invalidate.
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
The root problem is not packed support, you can read more in #431
In this case since USB registers are 16bit aligned, there is no need to put TU_ATTR_PACKED at top level (for example stm32_fsdev also has 16bit registers), put TU_ATTR_PACKED in the bitfield struct level will make the purpose more clear.
fallow birchBOT
fallow birchBOT
I did, the warning is still there
In my test there is no more warning moving TU_ATTR_PACKED to the bitfield struct level.
But since RUSB2_REG_t heavily use bitfield, I feel like adding TU_ATTR_PACKED everywhere is not elegant.
@hathach what's your opinion?
fallow birchBOT
In my test there is no more warning moving TU_ATTR_PACKED to the bitfield struct level.
Yeah, we should move the packed to bitfield if that fixes the issue. And also having TU_VERIFY_STATIC() to make sure the size of the whole struct is correct as well.
But since
RUSB2_REG_theavily use bitfield, I feel like adding TU_ATTR_PACKED everywhere is not elegant.
I don't real...
fallow birchBOT
However I have to changes the clock setup to use HSI48 (on B1) for USB device to run (existing code doesn't work with B1).
It must be because of this (I don't even remember when I soldered SB17), since B0 doesn't have CRS HSE must used.
Maybe no need to separate B0 board, just put a word to solder SB17 for B0 user.
Let me know if you are still planning to update this PR more, and p...
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
fallow birchBOT
