Search results

Thank you for the quick reply. I have done some further troubleshooting and realised the problem was actually just the IDE using previously compiled files. So long as a I make the changes with the IDE closed then launch and compile it is working as expected.

Thank you for the great work on this code. I have 8in 8out working at 44.1k, I am now trying to change this to be 2i4o at 96k, however any changes I make in the menus dont seem to have any affect. I have tried hardcoding USB_AUDIO_NO_CHANNELS_480 to 4 in usb_desc.h, and this then appears as a...

Hi Paul. Thanks for the reply. I eventually got to the bottom of the problem, there were a couple of issues. Firstly my poor soldering of 0.1mm cable onto the 0.5mm pitch pins, once this was resolved I could discover the IC and identify its type/capacity etc, but failed to initialise it...

Hi, I have been using this module from Adafruit in SPI mode and it works fine. I'm now looking to implement it on a custom board using it in place of the SD card on the Teensy via SDIO. I have removed the IC from the module and wired it up on a T3.6 to the microSD socket, though cant seem to...

Commenting here rather than starting a new thread as it seems a good place, is it possible to have multiple ltc objects reading from different inputs? For example one reading usb channel 0 and another reading usb channel 1. I've been trying but cannot get it to function. When I connect usb1...

Thanks for this, I'll take a look into this approach. I have however got it working now by changing the read_ascii_line function to read from the i2c Bus. The function waits in the while loop until an i2c packet is received, the upper teensy is transmitting one line at a time, so each time the...

Thanks for the direction. Where I'm getting lost is that the i2c_t3 library calls a function on a packet received event, so I don't know how to implement this into a stream class. I'll give it a go and see where I get to with it.

Hi, Heres an image to explain it a bit clearer. A T3.6 is used to convert USB Serial to I2C, on each /n an I2C packet is transmitted containing the HEX payload. Here is the sketch running on the converter T3.6, this seems to be transmitting fine, as running the basic slave example on the...

Hi, Has anyone had any success in impleneting FlasherX via I2C? I've currently got it working via RS-485 using a T3.6 to pass through from USB Serial to Serial1 with a max485 attached. However I'm struggling with the software side of things to do this over I2C. Currently my code will read...

Hi, I'm currently trying to run multiple SPI DACs at a high speed (around 30k updates a second) using T3.6. I'm using the AD5328 12Bit 8 Channel DAC, I'm trying to run 10 of these at the same time, using only 5 channels on each. My calculations for the SPI bus are as follows: 1x 16Bit word * 5...

Yes similar. I wanted my own unique id that was only 24 bits long.

They're on the target MCU, its an area in the flash that each block can only ever be written once. PJRC stores the S/N of each Teensy in here. I wanted to achieve similar for my custom boards for holding a S/N that can be used to create a unique MAC address. Theres not much Documentation on this...

Thanks for the reply. Thats what I've discovered since starting this thread. The RST pin of the MKL04 is now connected to pin5 of the 10-Pin ARM SWD cable, meaning that when the SWD lines are connected the Bootloader IC is held in a reset state freeing up the lines. I've also managed to code the...

Hi Josh, Can you provide any example code with this working? I'm having the same issue on a T3.6 where my compiled hex also contains some 4 and 8 byte lines, meaning that when I try to flash I get a flash block align error. Cheers.

I may be missing something here, but I’m coming up against a problem. I’ve built a board based around a custom teensy 3.6 using the boot loader chip. I’d like to flash my own serial number to the MK66 in the same way Paul does with the teensy’s, for this I’ve got a J-LINK SEGGER to connect via...

Hi All, So after being stuck in other projects for the last month or so, I've finally got round to building another test board with a revised PCB to include the changes mentioned above: Move traces under crystal Traces Added Vias in more places between Gnd Planes Reduced the separation...

Im Running OSX 10.14.5, And Kicad 5.1.4. Here are some updated files if anyone has a chance to glance over them for silly mistakes before I send to fab. Changes Include: Move traces under crystal Traces Added Vias in more places between Gnd Planes Reduced the separation distance on Gnd Plane...

I See it connected the same way as jonr with no errors in the DRC, plus can verify continuity on a PCB here. I'll add more GND vias, move the traces around the crystal, add decoupling to the MKL04 and then re-upload the project here so perhaps you guys can take a look before I send the boards to...

The pin13-PTC5 is intentionally not bought out, this board is purely to test a custom build. Strangely on my KiCAD it doesn't show a disconnect on the GND plane at that point.

Thanks for the suggestions. Here's a link to the library used for the MK66, I went through the data sheet to check the pins against this and couldn't see any mistakes. I think I'll make a revision to the pcb to move the traces under the crystal, check the usb length and add decoupling to the...

Heres a link to a Kicad project if you have chance to glance over that at all. I can't see anything obvious in the layout. https://www.dropbox.com/s/j8ysvsdnlyal5b7/Kicad%20Files.zip?dl=0

Hi Paul. Should be attached now, hopefully this is clearer. Thanks.

Hi, Ive been trying to build a custom Teensy 3.6, however it is non responsive. The 3.3V supply generated seems good. When pressing the program button I can see both the reset and program signal lines being pulled low. Attached is the schematic my board uses, I know it's not drawn the best...

Thanks for pointing that out. It kind of makes sense I think, so in the processResponderRDM() function I can specify a new case which is another RDM command as per the spec, which calls a function to build the correct response?

This is the library. There’s an example in there called dmx receive. Using this I can discover the teensy with a dmx tester. However I don’t really understand how to structure replies for other things such as remotely setting the dmx address or querying sensor values etc...

Hi, First post here, long time reader! Im currently using the Teensy DMX library on a T3.6 to receive DMX. Im trying to get RDM working, and have managed to get the example to work and can discover the teensy. What I'm struggling with is how to define additional commands such as reset, sensor...