I'll check on a scope again, the actual bit rate achieved, maybe I'm mistaken. I know I got garbled output, but that may have been on minicom, which doesn't do auto negotiations. Was flailing a lot today, getting frustrated with a lack of progress. If it really is auto negotiating, it would be worth looking at a faster interface.
Sorry, I could be wrong, but my guess is that there are very few devices/setups that auto-negotiate...
SDRAM test...
DMA Channel allocated 1
Buffer: 0 ADDR:0xc0000080 size:153600
Buffer: 1 ADDR:0xc00258a0 size:153600
Buffer: 2 ADDR:0xc004b0c0 size:153600
loop: 0(0) DMA: (65504 0 aa) (65505 0 aa) (65506 0 aa) (65507 0 aa) 88096
loop: 1(1) DMA: (65504 1 aa) (65505 1 aa) (65506 1 aa) (65507 1 aa) 88096
loop: 2(2) DMA: (65504 2 aa) (65505 2 aa) (65506 2 aa) (65507 2 aa) 88096
loop: 3(3) DMA: (65504 3 aa) (65505 3 aa) (65506 3 aa) (65507 3 aa) 88096
loop: 4(4) DMA: (65504 4 aa) (65505 4 aa) (65506 4 aa) (65507 4 aa) 88096
loop: 5(5) DMA: (65504 5 aa) (65505 5 aa) (65506 5 aa) (65507 5 aa) 88096
loop: 6(6) DMA: (65504 6 aa) (65505 6 aa) (65506 6 aa) (65507 6 aa) 88096
loop: 7(7) DMA: (65504 7 aa) (65505 7 aa) (65506 7 aa) (65507 7 aa) 88096
loop: 8(8) DMA: (65504 8 aa) (65505 8 aa) (65506 8 aa) (65507 8 aa) 88096
loop: 9(9) DMA: (65504 9 aa) (65505 9 aa) (65506 9 aa) (65507 9 aa) 88096
loop: 10(a) DMA: (65504 a aa) (65505 a aa) (65506 a aa) (65507 a aa) 88096
loop: 11(b) DMA: (65504 b aa) (65505 b aa) (65506 b aa) (65507 b aa) 88096
loop: 12(c) DMA: (65504 c aa) (65505 c aa) (65506 c aa) (65507 c aa) 88096
loop: 13(d) DMA: (65504 d aa) (65505 d aa) (65506 d aa) (65507 d aa) 88096$ brew install --cask tabby
I'll look into that. Thanks.
Yes, that seems to work, I discovered that this morning. I can use Tabby up to 1.5Mbaud that way.
$ minicom -C myfile.logThat would be the Easy solution to have both on TyCommander. One Tabbed or two TyComm Windows would give full access to both with two USB cables and the Two Teensys sharing UART.
Is there some reason you're avoiding logging to SD? It's got plenty of bandwidth.
Yes. Primarily because I cannot access the SD easily. This is inside of a box enclosure, with connectors and stuff, sitting on top of a lathe, which occasionally throws metal chips around. The chips can be long and stringy, or they can be tiny comma like pieces, but they can fly far, and end up in lots of places. Not a friendly environment for open Teensy boards!
Far easier than figuring out Ethernet on Teensy (not that it's terribly hard) and writing a custom program on my mac to read and save the stream... I'm really trying to stay on task, which is bug hunting, and finding out why there's synchronization loss. Profiling the code wouldn't hurt either.
Since I'm fishing for errors and clues, I can send far more data than the links can take. There's no trouble saturating the link if I want. Since there's no ICE for this board, I'm left with print statements, trying to figure out what, if anything, is wrong.
How does one add MTP to a build? Serial & MTP disk? Not clear that my Mac can do MTP without some help...
System started
0
0
10
13
83
116
97
114
116
32
116
105
109
101
32
61
32
52
50
51
51
52
56
54
54
49
10
13Loop = 2.380351667 msec
Loop = 2.380358333 msec
Loop = 2.380591667 msec
Loop = 2.380791667 msec
Loop = 2.381605000 msec
Loop = 2.383483333 msec
Loop = 2.380238333 msec
Loop = 2.380111667 msec
Loop = 2.380091667 msec
Loop = 2.380525000 msec
Loop = 2.381471667 msecOpps - that is what the example does - and I paired it down removing verbose 'comments' per character - but it is printing each character as ascii# one per line.
void loop() {
char incomingByte;
while (Serial.available() > 0) {
incomingByte = Serial.read();
// HWSERIAL.print("USB received:");
HWSERIAL.print(incomingByte);
}
while (HWSERIAL.available() > 0) {
incomingByte = HWSERIAL.read();
// Serial.print("UART received: ");
Serial.print(incomingByte);
}
}// set this to the hardware serial port you wish to use
#define HWSERIAL Serial1
void setup() {
Serial.begin(9600);
HWSERIAL.begin(2000000); // T_4.x might go to 5Mb, but higher will bring more interrupts on 1st
Serial2.begin(2000000); // T_4.x might go to 5Mb, but higher will bring more interrupts on 1st
}
elapsedMillis aTime;
void loop() {
char incomingByte;
if ( aTime > 2000 ) {
Serial2.printf( "Loop = %lu\n", millis());
aTime=0;
}
while (Serial.available() > 0) {
incomingByte = Serial.read();
// HWSERIAL.print("USB received:");
HWSERIAL.print(incomingByte);
}
while (HWSERIAL.available() > 0) {
incomingByte = HWSERIAL.read();
// Serial.print("UART received: ");
Serial.print(incomingByte);
}
while (Serial2.available() > 0) {
incomingByte = Serial2.read();
// Serial.print("UART received: ");
Serial.print(incomingByte);
}
}// set this to the hardware serial port you wish to use
#define HWSERIAL Serial5
void setup() {
Serial.begin(3000000);
HWSERIAL.begin(3000000); // T_4.x might go to 5Mb, but higher will bring more interrupts on 1st
Serial.printf("System started\n");
}
void loop() {
char incomingByte;
while (Serial.available() > 0) {
incomingByte = Serial.read();
// HWSERIAL.print("USB received:");
HWSERIAL.println(incomingByte);
}
while (HWSERIAL.available() > 0) {
incomingByte = HWSERIAL.read();
// Serial.print("UART received: ");
if ((incomingByte =='\n')) {
Serial.print(incomingByte);
}
if ((incomingByte !='\n')&&(incomingByte!='\r')) {
Serial.print(incomingByte);
}
}
}Start time = 394536081
Start time = 0.6575679483 seconds
Hello, FTDI is up!
|O�0, 516, 478957436
Loop = 6.291746667 msec
Loop = 2.379838333 msec
Loop = 2.379425000 msec
Loop = 2.380105000 msec
Loop = 2.379845000 msec
Loop = 2.379711667 msec
Loop = 2.379925000 msec
Loop = 2.380151667 msec
Loop = 2.380691667 msec
Loop = 2.379958333 msec
Loop = 2.380345000 msec
Loop = 2.380245000 msec
Loop = 2.379525000 msec
It's sufficient for what is needed at the moment. Who knows, I may be forced to figure out MTP on a Mac.IIRC the included PJRC '.println' sends both \r and \n - so that may be why it is there when only '\n' is needed - very annoying when cut and paste double taps them ... as bad a MSFT WORD default to non-single line spacing
Glad it is working as promised. Seems you did edits as the incoming serial pasted still has println to the UART - if you don't send any input there that is no issue and that Serial.available() clause could be removed,
I know your using a MAC but if you can use Windows on it you might consider looking at VisualMicro (VM) with Visual Studio.
I have a newer Mac. (M3) Windows doesn't run on it, nor do I wish to use some solution to allow it. Windows has run it's course in my home... Both my wife and I transitioned away from it around 2005. Did the Linux thing until late 2024, then went to a Mac. Every OS has it's issues, seen most of them.