Dont know if that has changed lately but in the past their libraries had horrible bad code... :)
I once saw a graphic driver and other libs and i decided not to spend time with this ... ok that was...
Type: Posts; User: Frank B
Dont know if that has changed lately but in the past their libraries had horrible bad code... :)
I once saw a graphic driver and other libs and i decided not to spend time with this ... ok that was...
Very interesting thing -I'd like to see your code?
I made something similar, but dont get much useful info.
My codes just resets after a hardfault.
Do you have an old 12MHz Hub? Don't know if that would work..I'm courious.
The way is to simply add an extra jack. Whatever you do - never connect the jacks GND to the normal GND. If you really want to go that way, cut all three connections.
The help in the Auio Library GUI says:
Then, you want to remove the SGTL500 Control.
15ma is way too much. I think its max 4mA for static DC for a single GPIO pin.
Not sure about PWM.
I partly agree. Teensy needs more pins. Not because one needs all pins, but because of missing functionality.
Then the question I would like to rise is, if really anyone needs 8 Serials... or which...
I tried that and can't confirm that. Looks like your Teensy has a defective pin.
@khoadley, if you look at the schematic - for Teensy - it seems you need to provide 3.3V to "VIO" (do NOT close JP7), and in addition the board wants 5V.
They even have connectors with inbuilt electronic ... filtering and EMI protection...
amazing!
23847
It's a bit expensive.. I think If I can find it somewhere, I'll order one and build an...
Found some great PDFs in German, from Würth Elektronik.
They say VBus (5V) should have a ferrite.
More advanced designs they propose have pretty complex schematics, just for the connector - with a...
Oh.. just noticed.. that the 4.1 has the TPD3S014 on board .. t4.0 not.
Seeing this the first time.. :) great.
Ok, on the Teensy 4, the 2 pins are just connected to GND.. I assume one is the GND wire in the cable, the other for the shielding?
So, that seems to be OK.
Sorry, I'm talking about the schielding of the cable.
The usb cable has GND wire, and a shielding that must somehow be connected to GND, too.
My Question is: Is the cable shield connected on...
Thinking of ground loops, EMI, etc:
A question re: USB Host
Should I connect the shielding of the USB Connector for the HOST to GND or is it better to do this not?
Is there a difference with...
Have you tried Pauls sketch?
Directly, no.
But you may ask the friends in this thread: https://forum.pjrc.com/threads/43165-Over-the-Air-firmware-updates-changes-for-flashing-Teensy-3-5-amp-3-6?highlight=flashing
You can't write the bootloader.
You can write to the teensy-flash,( but not to the bootlader )
That works with a normal Teensy - no extra booloader chip needed.
I've patched the denom value,
and added a search for the divs - now, more frequencies are working (if not all - tests needed)
Edit: really amazing that the PLLs work with up to 1.3GHz - tell...
I've added it here, with a link to this thread.
Yes, thats the same what the Reference manual says - everything but the max 960000.
I'll update that value. Thanx :)
Thanks!
The reference manual says not any word about this. (only that it can be 29 (or was it 30?) Bits wide) - I'll test if it makes any difference. As said.. the program works .. so i wonder if...
Hi,
AudioProcessorUsage() does not take the time needed for the DMA ISRs into account.
Some need quite a time (like S/PDIF emulation on Teensy 3.x).
I'd suggest a function like update_all()...
You may have seen setup() and loop()
Forget that.. they are just functions.
its something like
void setup() { your code here }
void loop() { your code here }
First of all, you should think about what you actually mean by "memory management".
Since you obviously know C, you know that there is at most new/malloc/free - and there is the stack, variables...
I'd check your desired frequency with a scope or frequency counter.
You don't want 44100Hz... there is no divisor for it.
Try 44117,64706Hz (there is no audible difference)
As said above: It works. As it is :) I'm aware that it fires twice.
Ok, didn't see that you use the DACs.
Which Teensy are you using?
Teensy 3.x with Audio Board Rev A to C uses pin 22 for Audio you use it for the LED.
Teensy 4.x with Audio Board Rev D uses pin 20, and 21 for Audio.. which are DC...
Hmm... not an expert here... electronics noob, still :)... but... this this sounds a problem with the current?
Is it worth to try and add a buffer-capacitor?
Can't you strip it down to the important parts? But it should work, so we that we can copy&paste it and try ..
Is it the same with the line-out connection?
Can you post the whole program?
These snippets do not help much..
Sounds interesting!
No, my code works.
Maybe do a copy&paste.. or try the transmitter as a whole.
May I ask what you're tryong to archive? Must be something with frequency modulation, too...?
Hm,
no, for the SD it's always the same pinout (for clock)
SPI-Mode:
23822
Not sure what it could be.. it's not audible, at least for me...
@Pauls (from Netherlands): If you're reading...
Yes, use more relaible connections - plug the shield directly on the Teensy - , don't use these china wires ;)
As Pin 44 is the SD clock pin, SPI wouldn't help.. needs a clock, too.
Or try the SD...
Take a look here: https://github.com/FrankBoesing/TeensyFMTransmitter/blob/main/output_fm.cpp#L159
Similar to yours... uses the timer @ audio sampling rate and uses the triggered dma to write to...
Just store it on SD? The waveplayer can play wav-files.
Maybe together with MTP.
You can record them in RAW format too. Maybe to SD, also. Or to PSRAM, or... wherever.
If there is no ready to...
Yup, I tried, but could'nt get more usable data to print.
At least it prints that something bad happened and what kind of problem it was. With a bit digging, it is possible to find where it was,...
Done that too.
Had to use the "Edge" Browser .... I never use that :)
Thanks, MJS.
No offense, really! - but usually "no response" or "no statement" means that something is unlikely to be adopted :) So, I don't spend more time for this. The weather is good - I enjoy the sun.
In...
also, for flash, perhaps just add the numbers for "data" and "headers"... the information "headers" is not that useful, i think.
Also, "free for files" is not correct. is can be used for code and...
I think two blank lines and a little formatting would make it clearer.
"C:\\Arduino\\hardware\\teensy/../tools/arm/bin/arm-none-eabi-objcopy" -O ihex -R .eeprom...
The Teensyduino installer is older than the new rules, that's all.
Havn't used it for years.. do we still support the eeprom-files?
If yes, they should be added.
Yes.. things like these are fun.
But for me, it's not that interesting. In addition, the VIC is very tricky. It has to be cycle-excact to be 100% compatible - I have it working in the emulaton,...
Well, it's a B-20
Serial.printf("Chip: Si47%d-%c%c%c\n", si4735.getFirmwarePN(), si4735.getFirmwareCHIPREV(), si4735.getFirmwareFWMAJOR(), si4735.getFirmwareFWMINOR());
Prints:
...not more.
I am quite disappointed and frustrated with this Si4735 stuff. This happens to me very very rarely.
After working wonderfully for a short time, it is now pretty much "dead". I2C...
It does not want 44.100 Hz :)
But this works (with the library mentioned above):
tone(0, 32000); // Output 32kHz on Pin 0 - connect Teensy Pin 0 with RCLK on Si4735
si4735.setup(RESET_PIN,...