Search results

Some years ago, I had the issue that Mouser did not sell Teensy4.1 to Germany. So far,I had no issue with Digikey, but this was before the PJRC-Sparkfun deal.

Ah, that is something to try. thanks.

This is really a question to Bill Greiman (creator of SdFat https://github.com/greiman/SdFat)

The following may (or may not) be related: while a SPI interface has the possibility to 'shut-down' the microSD card (I needed this to save power) unfortunately the sdio interface to the microSD card (Teensy4.1) has no possibility (at least I could not find one) to tell the microSD card that it...

I have a couple of digital Mems and I always wanted to do the beamforming thing in air (not allways underwater, which is so expensive). Maybe I will finally put it to work. As I need some additional challanges, I will first do it on T4.1 (the trivial part) but then on a RP2350 doing the I2S with...

Having done array processing and beamforming for over 40 years, I read with interest Claude and Codex observation. As to be expected, it is half science half phantasy (or non applicable). eg. time-delay-and-sum is indeed broadband and is 'frequency-blind'. Yes, but this is valid for all types...

Frank, a couple quick comments. I have not checked yet implementation but I like that you use franctional delays (with sinc function). No, You must be able to look boad side (all delays are zero). The beam pattern is defined by the overall aperture and when beam are plotted in cosine scale...

I would assume that your data are some-what correlated and would try to do some compression. I assume that you already pack 8 channels into 3 int32 words. As most data are typically less than 12 bit, you could pack more dense, by inspecting each (large) data buffer on the maximum bit depth...

Definitely the Audio board was a successful add-on, some improvements could have been possible (e.g. I had issues with digital interference on analog signal)

I would say that IS the main problem. Teensy is mainly a dev board, but not an ecosystem, like AF Feather or SF Thing Plus. The T3.5/6 ot T4.1 were great for me when I wanted to have a powerful single board MCU with SDIO. Yes, the Teensies have been used as MPUs in larger projects and products...

It does not matter what @whitebengal meant or not. I suggest that any thread on Adafruit vs Sparkfun (and this one) is closed immediately. If there is a need to enter into a Teensy development due to non PJRC events, than this should be named explicitely and focused on.

In the end, I find that the fact that the different contributions of @ptorrone to this and EEV forum (the ones I looked up) seem to be cut-and paste and all the personal details presented that better should be kept private, all this smells for me more an attempt to spread the AF-SF drama, and...

Cannot contribute, Windows11 pro here, Arduino2.3.6, No issues what so ever. OK, I did not download the exefile but used the boards manager.

As IMHO Paul (msg#150) made the right final statement, I strongly suggest to close this thread. Let AF continue on their own Forum on Freensy development.

For my sound recorder I have 2 designs one with Teensy4.1 and one with Adalogger RP2040. Software is nearly the same (yes, some hardware dependent moduls). I use the T4.1 for short high speed acquisition, where power is not an issue, but use the adalogger where power consumption is an issue...

Oh, yes. I have now detached the ADC and Preamp as seperate boards and have an LDO on the ADC board, and use as 5V source the USB-Host power, which has an own 100uF capacitor. For my application (underwater autonous recorder) the available space is rather limited. So everything is dangerasly...

I'm only interested in ADC. Here is an example I think professional developper can do better. Attached is a picture of a high performing Acoustic data acquisition system (Custom stereo piezo preamp + custom ADC +Teensy4.1 capable of acquiring stereo data at 384 kHz). Issues encountered with...

@jmarsh, what you are saying is the T4.x chip can be programmed without MKL. that is fine. We will not know the internals of the MKL chip and Paul will not chime in. So, I accept that you may be right with how the MKL potentially contributes to boot proceess.

I guess, this is not quite right as this chip makes a MCU to a Teensy. IOW, a board without this MKL chip can hardly be called Teensy compatible. AFAIK, in addition to 'turning power on', the chip - intializes the Hardware (https://www.pjrc.com/store/ic_mkl02_t4.html) - allow secure mode...

Independent of Phil's try (btw on Adafruit's Website is a picture showing Limor (with Baby) sitting in front of what seems to be the design shown also in post #1) I would be curious what will bring the future for Teensy. I assume Paul will not be able to disclose details from the agreement he...

Well, he came, addressed Teensy community with an idea, got an overall negative feedback, and left (at least for a day).

Well, I would say (add) that two things were important for me: One is the tripple role of the developper of Teensy (hardware, software development and forum support in a single hand) and second the community here that helped to solve a lot of problems. I do not know, how the future will be, as...

I'm not sure if I need a Teensy-compatible device from Adafruit. I use T4.1 for my high end application and I guess, I can still get them from Digikey. However, for my low-power-low-performance project I still wait for the Feather Adalogger RP2350, Limor has talked about last April (see my...

I was refering to what Bill Greiman commented on https://github.com/greiman/SdFat/issues/402 (Allocation and Recording Units). Acording to Bill a write alone does not sync().

A good data acquisition and logging system will have all processing at interrupt level and keep SD access at loop() level. This way waiting for SD write to return, does not matter. In particular, it does not interfere with acquisition that is handled at interrupt level. This is the beauty of ARM...

Even if you have a T4.1, I would try to write to an external uSD card. I know it is slower,but allows you to experiment with seperated power supply.

As evidenced by Bill Greiman, there is little the Teensy (any MCU) can do about activities on microSD card. Modern cards do use MUCH larger write-block-sizes. It is the card internal controller that decides what to cache and when to write. Writing single blocks only slows down the transfer speed.

What I did with a T4.1 + custom ADC board is to have on ADC-board an own 5V to 3.3V LDO and using as 5V source the USB-host 5V output. This has a 100 uF Capacitor, and as a bonus, can be switched on/off easily via software. Only the digital part of the ADC uses the 3.3V from Teensy board.The...

One thing I noticed a couple of years ago, the link order may not be the same as the include order, which is not an issue with Arduino, but with VSCode/VS2022 environments. original thread: https://forum.pjrc.com/index.php?threads/changing-include-order.44930/ I don't know if something in the...

This simply indicates that the VS2022 configuration does not point to Teensyduino but only to Arduino. (SD of Arduino does not know BUILTIN_SDCARD

I would try first #include <Arduino.h> #include <SD.h> void setup() { while(millis()<10000) {if(Serial) break;} if (!SD.begin(BUILTIN_SDCARD)) { Serial.println("failing SD.begin"); return; } } void loop() { } If this compiles and runs. then the issue is with one of the...

For low power acoustic data acquisition I use Adalogger RP2040 (Unfortunately the RP2350 that was said to be ready last April, did not show up in Adafruit's shop). One trick to reduce power is to use SPI and not SDIO to write to microSD and to write maximal buffer. This way the SD card could...

I use visual studio code (VSCode) with task extension, where I can switch between different configurations of VSCode and associated Makefile settings. key files are (in addition to Makefile) tasks.json c_cpp_properties.json

So Arduino button took you to Visual studio Code? To me that looks like a virus on your Linux? system.

remove "/home/wwatson/.cache/arduino/sketches/EFD8060CD376880344661705856FA353" (clean up previous compilation). maybe this helps

as @joepasquariello indicated you must use the Teensyduino version of SdFat as it differs slightly from official version. As these mods are only a few, you may edit the chillibasket version to line up with the Teensyduino version (I have done this in the past myself). Maybe deleting physically...

@charnjit As MTP_Teensy is now part of cores, you should delete your local copy (MTP_Teensy-pauls_branch under Arduino\libraries) to avoid confusion

My hunch is that for personal and on Windows use any PID should work. For example using the PID from USE_EVERYTHING (0x0476) could be a good candidate for testing and custom usb descriptor, as it is not implemented in T4.x (too many endpoints?)

The one in your modified descriptor. I would simply use 0x048B and try. Note when changing descriptor you need to press the boot button. Also, you should uninstall the COM ports (I do not have a Win7, so I cannot advice how, but google 'Windows 7 uninstall com ports' should give you...

PID mean Product_ID, as said in #22. Please read always what has been written so far.

@charnjit. Read Paul's answer #4 and #7 on number of endpoints. You can use my solution for testing. If there is something not clear, ask specific questions. For us to help you, you should show that you read and follow suggestions. We can and are willing to help you and do some testing ourself...

Well, I guess, I'm guilty on the define issue, when I constructed the USB_MTPDISK_SERIAL many, many years ago, But I agree it would be the time to revise the code to be more flexible.

I would have no issue with making a PR, e.g. creating a new USB device, say Audio-MTP-Serial with all the changes in core and boards.txt, but IMHO, the PID should be chosen by Paul and integrated into the upload procedure, so that the new PID is recognized and no Boot-button press is necessary.

This is working for me (Arduino 2.2.6 /TD 0.60.5) #include <Audio.h> #include <MTP_Teensy.h> AudioInputI2S acq; AudioOutputUSB usb1; AudioConnection patchCord1(acq, 0, usb1, 0); AudioConnection patchCord2(acq, 1, usb1, 1); #include <SD.h> #include...

not sure if #define CDC_DATA_INTERFACE 1 // Serial and #define AUDIO_INTERFACE 1 // Audio (uses 3 consecutive interfaces) is correct

Reading Paul's comment correctly, you should not use seremu, but serial i.e. (CDC or MTP Serial experimental)

I guess, you should update to TD 1.60.5 (latest beta). If then you have issues, Paul can check/advice

Suggest to use MTP_Teensy https://github.com/PaulStoffregen/MTP_Teensy which is build on my version but is modified to interface better with Teensyduino ongoing development

@alizeh maybe https://www.micropam.com/microPAM-T4_hardware.html gives you some ideas

I would add a 'third option' to handle latency issues of SD cards, which is the one I'm using in my high speed data logger (mega-samples/second). - allow blocking How? use the leveled interrupt system (as RTOS have done since last Millennium) in particular, - run in loop() ONLY code to access...