K66 Beta Test

Status
Not open for further replies.
All I saw was the F_CPU... line. Not sure what all you are expecting as I don't have any sound hardware installed. Will try again probably in morning.
 
OK, thanks Kurt.
At a minimum, this code does need the audio board to be installed to test whether the code will start properly or not.
In order to play with it you also need a microphone.

Pete
 
el_supremo said:
OK, thanks Kurt.
At a minimum, this code does need the audio board to be installed to test whether the code will start properly or not.
In order to play with it you also need a microphone.

Pete
Click to expand...

PJRC just sent me a MIC for my audio board - now I lost my audio board - I have downloaded voc....zip - will look for the Audio board and solder on the mic and give it a try. {found}
 
Last edited:
I've just tried it using Arduino 1.6.9 and TD 1.29 with the same results. It works if the program is under 512kB and doesn't start up at all if it is over 512kB.

Pete
 
I got my K66 beta board today. Thanks for including me on the beta list. Due to migraines, I haven't done anything with the K66 at this point.

I was curious about the second DAC channel. DAC0 presumably would be the same at the library level as the single DAC (A12 in the Teensy LC and A14 in the Teensy 3.1/3.2) in previous Teensys. I looked into beta2 of the 1.30 release, and I don't see any support yet for the second DAC channel. Now, perhaps it is there, and I'm missing it, as I was just doing a cursory search of the includes and libraries.

Similarly, the current audio design tool doesn't have support for a second DAC either.

I assume these things will come in time, perhaps in the final 1.30 or maybe 1.31, but is my assumption correct that only the first DAC is currently supported?
 
Compile and upload 9 loops under 180, then 180 then 240 MHz with 11 loops no problem on Proto_6 board.

IDE 1.6.9 :: Win10x64 :: TD 1.30_beta 1

Short 'organ' sound brushing finger over mic and more so blowing across the mic?
Volume knob works to raise volume - can hear some sustain sticking in there?

No problems 5 uploads works at 180 and 240. {both proto_6 and round_3 T_3.6}

Sketch uses 617,716 bytes (58%) of program storage space. Maximum is 1,048,576 bytes.
Global variables use 51,024 bytes (19%) of dynamic memory, leaving 211,120 bytes for local variables. Maximum is 262,144 bytes.
Click to expand...

C:\tCode\T3_K66\AUDIO\vocoder_16rec_9fx_SF_6_rectify\vocoder_16rec_9fx_SF_6_rectify.ino
F_CPU = 180 MHz
Found 11 loops
Loop = CARRIER22
setup done
CASCADE_2
bp_base = 100.0, bp_width = 400.0
mixer18_gain = 4.0, mixera_gain = 3.0
Using MICROPHONE input
Proc = 55.72 (55.72), Mem = 25 (29)
Proc = 55.09 (55.78), Mem = 25 (29)
Click to expand...

C:\tCode\T3_K66\AUDIO\vocoder_16rec_9fx_SF_6_rectify\vocoder_16rec_9fx_SF_6_rectify.ino
F_CPU = 240 MHz
Found 11 loops
Loop = CARRIER22
setup done
CASCADE_2
bp_base = 100.0, bp_width = 400.0
mixer18_gain = 4.0, mixera_gain = 3.0
Using MICROPHONE input
Proc = 41.78 (41.78), Mem = 25 (29)
Click to expand...

<EDIT> compiled again fine and a bit more soundy effectiveness with >> audioShield.micGain(30);
 
Last edited:
MichaelMeissner said:
... is my assumption correct that only the first DAC is currently supported?
Click to expand...

bummer on the head thing - Not sure if this is responsive? :: the only DAC use I tried was for TALKIE.cpp when FrankB expertly adjusted as below and I tested A22 to work just as well in that case as A21.

Code: 
#if defined(__MKL26Z64__)
	analogWrite(A12, nextPwm);
#elif defined(__MK20DX128__) || defined(__MK20DX256__)
	analogWrite(A14, nextPwm);
#elif defined(__MK64FX512__) || defined(__MK66FX1M0__)
	analogWrite(A21, nextPwm);
#else 
	#error "Unknown Teensy"	
#endif
 
defragster said:
bummer on the head thing - Not sure if this is responsive? :: the only DAC use I tried was for TALKIE.cpp when FrankB expertly adjusted as below and I tested A22 to work just as well in that case as A21.
Click to expand...

Ok, it sounds like the low level analogWrite works on either DAC. I was thinking of the higher level at the audio library, there currently doesn't seem to be any code to handle two DAC's. I assume ultimately, there might be an optional argument to give the DAC # to output_dac, or a parallel function for the 2nd DAC. Given the amount of stuff added to the K66, I can understand that it would be a much lower priority than some of the other stuff.
 
Sorry if it is just me, but wondering about the USB serial numbers or the like. I was noticing some stuff on windows, that I wanted to verify and so I installed Arduino 1.6.10 (actually already had), plus beta2 (was beta1) on my MAC. I updated the boards.txt to one for T3.6...

Loaded up blink.ino and plugged in the T3.6 and went to choose the Serial.port:
It turned out to be: /dev/cu.usbmodem1 which does not sound overly unique?

I tried plugging in two T3.2s and they showed up /dev/cu.usbmodem170971 and ....1550131
Likewise I tried a TLC and saw: ...457241

Wondering now about what lsusb on linux will show.

Update: Pulled out my notebook with Ubuntu 14.04 installed and see:
That when I used a T3.2 and typed in: lsusb -v -d 16c0:0483 it shows a bunch of stuff including:
iSerial 1701970
When I do same thing with T3.6: iSerial is 0

Maybe just a beta process not setting serial # ?
 
Last edited:
KurtE said:
Wondering now about what lsusb on linux will show.
Click to expand...
Here is what I got. Note, I plugged in the 3.6, 3.2, and 3.0 at different times, so the device number will be different. On the 3.6, this is using the standard USB, not the secondary USB that can be added via the internal pins.

If it matters, I am on a Fedora 22 system. I used Teensy 1.30 beta 2 to compile the 3.6 and 3.0. The 3.2 was programmed with either 1.30 beta 2 or 1.30 beta 1. I don't recall when the LC was programmed.

  • Teensy 3.6: Bus 001 Device 038: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
  • Teensy 3.2: Bus 001 Device 039: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
  • Teensy 3.0: Bus 001 Device 040: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
  • Teensy LC: Bus 001 Device 044: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial

Lsusb -v on Teensy 3.6 shows:
Code: 
Bus 001 Device 043: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.01
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x16c0 Van Ooijen Technische Informatica
  idProduct          0x0483 Teensyduino Serial
  bcdDevice            2.00
  iManufacturer           1 Teensyduino
  iProduct                2 USB Serial
  iSerial                 3 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x01
          call management
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x06
          sends break
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              64
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Lsusb -v on Teensy 3.2 shows:
Code: 
Bus 001 Device 041: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.01
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x16c0 Van Ooijen Technische Informatica
  idProduct          0x0483 Teensyduino Serial
  bcdDevice            2.00
  iManufacturer           1 Teensyduino
  iProduct                2 USB Serial
  iSerial                 3 1937660
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x01
          call management
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x06
          sends break
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              64
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000

Lsusb -v on Teensy 3.0 shows:
Code: 
Bus 001 Device 047: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.01
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x16c0 Van Ooijen Technische Informatica
  idProduct          0x0483 Teensyduino Serial
  bcdDevice            2.00
  iManufacturer           1 Teensyduino
  iProduct                2 USB Serial
  iSerial                 3 28780
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x01
          call management
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x06
          sends break
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              64
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

Teensy LC shows:
Code: 
Bus 001 Device 044: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x16c0 Van Ooijen Technische Informatica
  idProduct          0x0483 Teensyduino Serial
  bcdDevice            1.00
  iManufacturer           1 Teensyduino
  iProduct                2 USB Serial
  iSerial                 3 1122030
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x01
          call management
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x06
          sends break
          line coding and serial state
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              64
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
 
Thanks Michael,

Yours show iSerial = 0 as well.

After I posted this, I noticed that Paul did a delta a few days ago to the function to get the USB serial number. So I updated my cores to the current code, rebuilt blink again, checked it out on Linux machine still showed serial # of 0...

Then I looked at the changes and saw:

Code: 
void usb_init_serialnumber(void)
{
	char buf[11];
	uint32_t i, num;

	__disable_irq();
#if defined(HAS_KINETIS_FLASH_FTFA) || defined(HAS_KINETIS_FLASH_FTFL)
	FTFL_FSTAT = FTFL_FSTAT_RDCOLERR | FTFL_FSTAT_ACCERR | FTFL_FSTAT_FPVIOL;
	FTFL_FCCOB0 = 0x41;
	FTFL_FCCOB1 = 15;
	FTFL_FSTAT = FTFL_FSTAT_CCIF;
	while (!(FTFL_FSTAT & FTFL_FSTAT_CCIF)) ; // wait
	num = *(uint32_t *)&FTFL_FCCOB7;
#elif defined(HAS_KINETIS_FLASH_FTFE)
	// TODO: does not work in HSRUN mode
	FTFL_FSTAT = FTFL_FSTAT_RDCOLERR | FTFL_FSTAT_ACCERR | FTFL_FSTAT_FPVIOL;
	*(uint32_t *)&FTFL_FCCOB3 = 0x41070000;
	FTFL_FSTAT = FTFL_FSTAT_CCIF;
	while (!(FTFL_FSTAT & FTFL_FSTAT_CCIF)) ; // wait
	num = *(uint32_t *)&FTFL_FCCOBB;
#endif
And noted the comment does not work in HSRUN mode, so I rebuilt blink at 72mhz and Windows decided to give me a new comm port. Looked over at linux machine and I now have an
iSerial of 4294967295...

So looks like a known problem.
 
defragster said:
Short 'organ' sound brushing finger over mic and more so blowing across the mic?
Click to expand...
Yep. Talk into the mic. Also, if you put a button on pin 28 (or just ground a piece of wire from pin 28) it switches to the next loop.

Volume knob works to raise volume - can hear some sustain sticking in there?
Click to expand...
I can't figure out where that "sustain" comes from - it isn't intentional. The only thing I can think of is that it is something to do with the biquad filters. Although, the mic I am using is very sensitive and in my case perhaps it is picking up the constant fan noise from the desktop computer.


No problems 5 uploads works at 180 and 240. {both proto_6 and round_3 T_3.6}
Click to expand...

Thanks for doing this. For now, I'll have to assume that it is something to do with the round 1 K66 unless one of the others with a round 1 can try it and get it to work.

Pete
 
PROBLEM HERE ???

Pete - turns out I have both {both proto_6 and round_3 T_3.6} - and last night I swear I tested both to work. The Rnd#3 board ran fine over night. Going back to Rnd#1 board - it uploads and goes offline with no serial output? It won't run the Vocoder sketch - even at 96 MHz to complain about the speed?

I put on another sketch - so the board is fine - both using same Audio Adapter - nothing else actively connected.

Now Rnd#3 won't run and give warning at 96 MHz - I know I saw that last night.

Now back to 180 MHz - NEITHER board will run the VoCoder with 11 loops.

Both took upload and run at 9 loops and ran fine.

Back to 11 LOOPS and Neither will run to show any USB output! TYQT shows them 'Missing' - they never come online.

I did more 512+MB uploads to the R#3 board than R#1 - but R#1 stopped first :: IIRC
 
defragster said:
Going back to Rnd#1 board - it uploads and goes offline with no serial output?
Click to expand...
That's the problem.

Now Rnd#3 won't run and give warning at 96 MHz - I know I saw that last night.
Click to expand...
Oh, oh. That sounds ominous. But the vocoder needs a lot of cpu for the audio processing and 96MHz is too slow. On the T3.6 you should run it at 180MHz. This version of the vocoder won't run in a T3.2/1 because of the ram space requirement unless it is compiled with only one of the smaller loops. But then the processor must be overclocked at 144MHz.

TYQT shows them 'Missing' - they never come online.
Click to expand...
When that happens to me (BTW - this is on Windows 7 Pro), I hold down the reset switch, compile and upload the Blink sketch and, once it has uploaded, release the button. That has always revived the serial port in Win 7 for me.

Pete
 
Pete:: Indeed - something off. Worked fine both boards a couple/few times, then over 512MB/11 loops and no go, no matter what.

Believe me I plugged and unplugged both boards multiple times with button press and intermediate sketches uploading. Something that was working with 11 loops stopped, and still works with same code and 9 loops.

And the 96MHz test was known to act odd - I posted that last night - and that behavior never shows - the thing halts somewhere before it starts serial.

Last I tried failed at 11 loops, re-commented #7 & #10 and it worked again.

Paul - I suspect you can see what I saw with an audio board and either K66. Take the prior posted code. Make the edits to uncomment lines in loops.cpp. Upload it 5-10 times?
 
I wondered if it was something to do with setting up the serial, so as a first test I commented the while(!Serial) statement and tried to upload with >512kB ram but it failed. I then commented everything to do with Serial and tried again and still no go. [+EDIT] i.e. the serial port disappears and the program doesn't run even though it doesn't use the serial port.[/EDIT]
It seems to be overwriting something during the upload process.

Pete
 
Last edited:
I don't have audio-shield, so i tried to make a simple bigflash sketch, just printing out values from the big const vectors. Alas, if the size of my arrays was bigger than 330K, the compile failed
Teensy Loader could not find the file bigflash.ino
Oh no, the compiler quit with an error, but did not print any error messages!
Your computer may be running out of memory or resources. Try closing other
windows or programs
Error compiling for board Teensy 3.5
Click to expand...
This was on ubuntu 14.04, 1.6.9 with 1.29-beta4 (with recent teensy core updates). so my environment may have other problems, and probably not relevant to the vocoder issues. But it might be of interest to see if the problem can be demonstrated with a simpler sketch...
 
Last edited:
I got some of compiler stuff like that a time or two, but many more it worked, and then it stopped working on both 100% for 11 loops, and fine on 9 loops. Win.10,ide 1.6.9.

When I get back to it I'll restart my machine, and open a fresh copy of the zip, but it seems for now a few uploads and something is set bad?

I can resample my fft to video code that before was limited for a T_3.2 and see if it works
 
Here's a simple sketch which demonstrates the problem without any need for an audio board or microphone.

Code: 
const short array[256*1000-36000] = {43};
void setup()
{
  Serial.begin(9600);
  while(!Serial);
  delay(1000);

int32_t sum = 0;
for(int i=0;i<rand();i++) {
  sum += array[i];
}
Serial.println(sum);
}

void loop()
{
}

With the -36000 in the array size declaration, the code was 463,420 bytes long and loads and executes without problem. Remove the -36000 and the code size becomes 535,420 bytes, the sketch won't run and the serial port disappears.
The summation is a ploy to stop the compiler from optimizing the entire array out of existence.

Pete
 
Quick update - we're planning to have the Kickstarter campaign go live tomorrow (Aug 17) at 8 am pacific time.

The moment the Kickstarter page is up, it'll be ok to post pictures, even share on social media. Just about 15 hours to go...
 
I've done some more testing to try to get to the bottom of the MIDI problem, but with no luck. However, I am sure that MIDI-Ox and my own midi routing program are not causing the problem. My program can route the 61es keyboard to the Microsoft GS wavetable synth and I can play on it (it's really awful though [*]) and leave it running for long periods of time with nothing untoward happening on the PC.

>>> I have run into another MIDI-related problem with the K66. Although I can get USB MIDI working on its own, I cannot get Serial+MIDI to work. I've been using the PrintIncomingMIDI example on the Teensy LC with Serial+MIDI and it works - I can play on the keyboard and the note on/off messages appear on the serial monitor. But that same program will not work on the K66. The Serial port is always dead and nothing I've done to it will revive it. I can always bring it back if I set the USB back to Serial only and run the blink program. But if I set the USB to Serial+MIDI and try to upload the example again, the serial port disappears.

When I first tried using the Teensy LC, it had to load a Windows Teensy driver for the MIDI - I hadn't used that LC for MIDI before. After that, it uploaded the example code and I noticed that there were a lot of conhost and Teensy_gateway processes so I unplugged the LC and keyboard before things got out of hand. There were 88 conhost processes and 87 teensy_gateway processes. One of the teensy_gateway processes was using 100% of one cpu so I killed it. I decided to just reboot so that I could start afresh. After the reboot I tried the LC with the Serial+MIDI example again and had no problems with it.

The conhost process seems to be created just after I hit the button in the IDE which does compile and upload. If I have the reset button pressed during compile/upload the conhost process disappears as soon as I release the button to let the upload proceed. I haven't been able to determine when the teensy_gateway is created nor when it usually dies.

Pete
[*] I am referring here to both my playing, which is always awful, and the microsoft GS synth which is laggy and sounds atrocious.
 
el_supremo said:
Here's a simple sketch which demonstrates the problem without any need for an audio board or microphone.

Code: 
const short array[256*1000] = {43};
...

Pete
Click to expand...

Indeed this failed to show on USB after upload. Same result with TeensyDuino and TYQT uploading.

I am back to my machine now - post 1072 questions tomorrow - have to get ready for Kickstarter in 10 hours!
 
Status
Not open for further replies.
Back
Top