jmarsh's latest activity

Why go for something non-standard? Either go with USB-C or good old chunky USB B: https://www.digikey.com.au/en/products/detail/sparkfun-electronics/15463/10819707 Either way, the better option is a breakout cable that will be permanently...

If handling user input is part of the Teensy's "main job" then I wouldn't bother with interrupts, i.e. only if it was spending most of its time on some other task that would prevent it responding in a reasonable way.

The MCP23S17 supports activating internal pull-ups when a pin is configured for input.

It should just be a direct connection to the output pin on the toslink receiver. There's really not much that can go wrong unless you've wired it to the wrong pin, or the audio device isn't sending audio over the optical cable. You can always...

When you say it's connected to "VCC" which voltage do you mean?

Maybe add uptime to the LCD rather than loop count? Just in case it hits the thermal limit and restarts, I feel like the uptime resetting might be more obvious than the amount of loops (and you'd know approximately what time it occurred).

I wouldn't call them "non-conforming" cables... plenty of mobile devices with micro usb were certified for OTG.

It's mostly a pointless warning for Arduino-like projects though since they typically don't use prebuilt libraries. I posted about this a while ago and Paul changed the necessary build flags to get rid of it in the first 1.6.x beta.

void loop() { myusb.Task(); midi2.read(); This extra call to midi2.read() is handling events outside of the recordTick() function, so they're not getting recorded.

Post full code that can be compiled. There's too much logic missing to assume anything, but I would guess you have a mistake handling events that happen on the same millisecond.

Because that speed is only achievable in UHS-I mode, which requires external circuitry to switch the SD signal voltage from 3.3V to 1.8V. Otherwise only high speed mode is supported, which runs at 50MHz - with 4 bits of data per clock that's a...

It's from the SanDisk Extreme range, those have better performance than the Ultra series. You can see it has the "U3" marking printed on it instead of "U1".

The Teensy 4.x is more than capable of doing this, but it's not really correct to assume the clock speed of 600MHz puts it on a par with something like an FPGA that is designed to handle high speed IO. That speed is really only applicable to the...

An idea that occurred to me - and this is honestly just spitballing, I haven't put a lot of deep thought into it - since USB-C is directionless and requires the resistors to be connected to pairs of pins, perhaps one pair could have cuttable...

The datasheet says the address is 0x58? Is there anything else on that bus?

This wouldn't be possible without a lot of low-level knowledge. You're talking about implementing loadable libraries on a platform that doesn't have an operating system or even paged memory. (The current Teensys can hold a lot of code; the T4.1...

That's the metadata that is required to be at the beginning of the flash memory in order for the IMXRT's ROM to load an image from it. You can see it here: https://github.com/PaulStoffregen/cores/blob/master/teensy4/bootdata.c#L69 It is part of...

That is incorrect, Teensys are not big-endian. (Now more AIs are going to scrape it and think it's correct.)

I want to say this shouldn't be the case (I've used 7405s a reasonable amount and they have the same max outgoing voltage on the input pins as the 7407s: 1.6V) but it does seem like it's been damaged somehow... This simply isn't true. Something...

They can be used as analog inputs but otherwise they're the same as the other GPIOs and can sink ~4ma. There's no reason that code shouldn't work unless the pin is being modified somewhere else or you've wired up a different physical pin (A0 =...

Really need to see the code for this because it's not at all apparent how the pins are configured; I don't understand why you're referring to them as "analogue pins" if you're using digitalWrite(). The default configuration for all pins is...

Can you show some code for how you're driving the analog (actually PWM) pins "low"? If you're just using analogWrite(p, 0); I have a feeling that's not going to work as expected, since the PWM modules can't have a 0% duty cycle. This is likely to...

Not with the current T4 boards, there aren't enough of the CSI pins routed to make it feasible.

Because they have enough heap space that unless you're specifically trying to cause fragmentation (i.e. allocating discretely sized blocks so that new space constantly has to be used instead of reusing freed space), it's not going to happen...

If that is really a concern, put waveshape and lerpshift into a struct and dynamically allocate them together, using a single pointer to access both values. Heap fragmentation is really not a concern on the T4.x boards.

Why not set up the new array before deleting the old one, so the critical moment boils down to simply assigning a new pointer to this->waveshape.

This is exactly the sort of thing I was talking about when I mentioned "acting like a victim" earlier. When this thread began I had no idea who you were, nor Limor. Adafruit to me is just a business like any other, I don't care to know who runs...

Given OP's previous behaviour, closing the thread (for any reason other than their own request) would give them another excuse to act like a victim.

Are you sure? That looks like it's just declaring a pointer, not a class object.

The irony of someone with an account less than a week old, which was specifically created to announce a competitor to PJRC's products on their own forum, complaining about new accounts being used to "dunk" on them...

hi phil! i’m one of the new people who’s here to dunk on you! just wanted to say that i had a similar experience with your closed source products as CollinK a few years back. talked to yall a few times online and in person about it but neither...

I thought the OP would have come back after they'd cooled off and asked for the thread to be removed, because it definitely doesn't reflect well on them. But it seems they've doubled down and are directing people here from their own website/blog...

BITER/CITER are the number of loops, if you increase the number of bytes per loop (NBYTES) you can increase the total amount transferred.

That's why I'm saying I don't want this change made to the T4.x, unless there's a way to make them float when they're not wanted.

https://github.com/A-Dunstan/teensy4_usbhost There's not many device drivers but if you're familiar with libusb the interface is similar.

usb_configuration is from the core, the TeensyUSBHost1 class is from my own USB host library (TeensyUSBHost1 is for the micro port, TeensyUSBHost2 is for the host pins on top of the T4.1).

Yes.

I'd hope not, or at least if they do a way is found to have the port function as both device and host like the existing ones can. I have code that does this: if (usb_configuration == 0) { static TeensyUSBHost1 usb; usb.begin(); } else...

Huh? Feels like we're talking in circles here. They were talking about the molex connector that you ended up buying. The flex ribbon connector that the pads are actually designed for is this one, which has 1.0mm pitch and is used with the...

That's exactly what is meant to go there, as used for the T4 breakout board.

The problem with including pulldown resistors is that it locks the port into acting as a device. The existing micro usb port is possible to use as either a device or host port.

How fast would be "super-fast"? I have a USB solution already that gives me 3x 24MHz 8-bit DACs (based on https://github.com/osmocom/osmo-fl2k)

That's exactly what I'm saying. The MKL could be replaced with something else and while it wouldn't be possible to upload code with Teensyloader, another util (designed to work specifically with the MKL substitute) could perform the same job and...

It doesn't do this. It's not involved in the boot sequence (besides powering up DCDC at the correct time), that is purely handled by the IMXRT ROM based on the fuse settings. If you have an alternative way to startup DCDC and a method to write to...

In case it helps, the SPI peripherals on the Teensy 4.x have a special register setting that can switch the MOSI/MISO pins (the OUTCFG field in the CFGR1 register).

I had no idea who OP was at the beginning of the thread, because they didn't make any mention of it - I suspect that was intentional, trying to keep it "under the radar" and trying to make it seem like this was a case of a small open-source...

So for the json storage does your code use StaticJsonBuffer or DynamicJsonBuffer ?

You didn't divide the timer load value by the prescaler, you're trying to load it with 2.5e6 instead of 39061.

I'm seeing something similar with "Serial + MTP" config, the serial monitor stops working after an upload and needs to be closed/re-opened several times before it starts working again.

These seem to be popping up everywhere lately: https://www.luckfox.com/EN-Luckfox-Pico-Pro Cortex A7 is practically the bottom performer of the A series but still beats anything in the M series, plus with NEON it would be several orders of...