Sounds great, but in the mean time wondering how difficult it would be to at least get some basic Serial.read() code to work... Maybe with just one fixed buffer or... Otherwise I will probably continue to do most of my debug work using HardwareSerial ports...
I think the version I have is the previous 5.0 document, looks like 5.1 is up there now: https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=457080
- it seems to be working fine fixing my problem above - both on T4 and T_3.6.Yes HardwareSerial:
Code:int HardwareSerial::peek(void) { //… } int HardwareSerial::read(void) { //...}
#define SER_IN Serial1
void setup() {
SER_IN.begin(1843200);
while (!SER_IN && millis() < 4000 );
SER_IN.println("\n" __FILE__ " " __DATE__ " " __TIME__);
}
float val;
void loop() {
SER_IN.print("Enter a number - float if you please = ");
while (SER_IN.available() == 0) {}
val = SER_IN.parseFloat();
SER_IN.print("You Entered=");
SER_IN.println(val);
if ( 13 == SER_IN.peek() ) { SER_IN.read(); SER_IN.println("Ate the C_Return!"); }
if ( 10 == SER_IN.peek() ) { SER_IN.read(); SER_IN.println("Ate the NewLine!"); }
}T:\arduino-1.8.8T4_146\hardware\teensy\avr\cores\teensy4\debugprintf.c :: void printf_debug_init(void)
// LPUART3_BAUD = LPUART_BAUD_OSR(25) | LPUART_BAUD_SBR(8); // ~115200 baud
LPUART3_BAUD = LPUART_BAUD_OSR(12) | LPUART_BAUD_SBR(1); // 1843200 baud
https://www.nxp.com/docs/en/reference-manual/IMXRT1050RM.pdf
//Enable CAN2 Clocks
CCM_CCGR0 |= CCM_CCGR0_CAN2(CCM_CCGR_ON) | CCM_CCGR0_CAN2_SERIAL(CCM_CCGR_ON);
Serial.print("CCM_CCGR0: ");Serial.println(CCM_CCGR0, BIN);
//Set clock source to 24Mhz with a 0 div
CCM_CSCMR2 = (CCM_CSCMR2 & 0xFFFFFC03) | CCM_CSCMR2_CAN_CLK_SEL(1) |CCM_CSCMR2_CAN_CLK_PODF(0);
//rx configure pin for flexcan2, pin0 (AD_B0_03)
CORE_PIN0_CONFIG = 0x10; // alt 0 is can2, sion = 1
IOMUXC_FLEXCAN2_RX_SELECT_INPUT = 0x01; // set pin for input
Serial.print("IOMUXC_FLEXCAN2_RX_SELECT_INPUT: ");
Serial.println(IOMUXC_FLEXCAN2_RX_SELECT_INPUT, BIN);
//pin1, can2TX AD_B0_02
CORE_PIN1_CONFIG = 0x10;
//Set Control pad configurations.
//uint32_t fastio = IOMUXC_PAD_SRE | IOMUXC_PAD_DSE(3) | IOMUXC_PAD_SPEED(3);
CORE_PIN0_PADCONFIG = 0x1A081;
CORE_PIN1_PADCONFIG = 0x1A081; //0x1f038, 0x1A081, 0x10B0, other configs tried.
Serial.print("Core PINS: "); Serial.print(CORE_PIN0_CONFIG, BIN);
Serial.print(", "); Serial.println(CORE_PIN1_CONFIG, BIN);T3.6 @240 MHz - 334ms
T4 - 76 msIOMUXC_SW_PAD_CTL_PAD_GPIO_AD_B1_02 = 0xb0;
Added a pull-request for MQS.
My fork has all new changes: https://github.com/FrankBoesing/Audio
You can directly add small speakers (8 OHM) with a capacitor in series (I used 100uF) - It is not very loud, but in a quite environment it is ok.
Maybe one of you electronic-specialists could post a simple amplifier? a one - transistor thing?
I'm not sure if I have the frequencies right - at least I have one more output working now.
// teensy4 mqs frank's audiolib pins 10/12 rt/left
// start monitor to hear sound, hit key to increase freq
#include <Audio.h>
// GUItool: begin automatically generated code
AudioSynthWaveformSine sine1; //xy=180,469
//AudioSynthWaveformSineHires sine1;
AudioOutputMQS mqs1; //xy=380,468
AudioConnection patchCord1(sine1, mqs1);
// GUItool: end automatically generated code
int freq = 1100;
void setup() {
Serial.begin(9600);
while (!Serial);
Serial.println("Setting up");
AudioMemory(12);
sine1.amplitude(1.0);
sine1.frequency(440);
Serial.println("Send Serial Char to increase freq");
}
void loop()
{
#if 0
if (Serial.available()) {
Serial.read();
sine1.frequency(freq);
Serial.println(freq);
freq += 100;
}
#endif
}
You can use a built-in pullup or pulldown to keep an input from floating near Vdd/2 where MOS gates have excess power dissipation. A "keeper" automatically switches between pullup or pulldown depending if the pin is above or below midpoint. Doing this minimizes power draw either way; the docs say minimum power consumption was a priority in the design of this part. But you don't want such a keeper mechanism active on an analog ADC input, because even a very weak pullup/pulldown current puts a (perhaps small) kink in your transfer curve, unless you drive the pin with a very stiff voltage source.
Wow. Thanks for the offer. I am only testing USB right now, no underside pins, so maybe about 8 or so. Don't want to push my luck
so maybe about 8 or so. Don't want to push my luck
9 buttons, slider, 2 joys and 4 way direction all came through.