Search results

just a small suggestion that can be usefull with minimal code needed and added to the installer: adding a selction for creating shortcut to the desktop for the audio design tool if the audio lib is installed? [ also, just got around to use the forum again :P ]

hm.. ok, so i basically need to stick with my teensy 3.2 until the core libs get rtos support (luckily i can wait) too bad i can't help you with testing :( (and indeed, this is a bit offtopic) regarding the sdram: will there be a possibility of a teensy version with it and one without? (like...

freertos as bare bones system yes, but i doubt compability with the teensy core libs.

tbh i'm still sticking with the teensy 3.2 until a proper rtos support is integrated (the teensy 3.2 has the freertos port for the arduino ide!) some things i wonder about the mcu for the next gen teensy mcu: (maybe i can ask nxp directly for these questions) why 'only' 512k ram, ideal would be...

true that, it also has less computational power, but it also has less power draw (the package states power: 30mA) but the ram is twice and rom is same as a teensy 3.6

hi all, i don't know, but it seems the teensy series are a bit overpriced compared to the competition? as i found a cortex m3 with 80mhz cpu 512k ram, 1024k flash, wifi, which is breadboard friendly and includes a serial programmer for a total price of $5,50 (rounded upwards) excluding...

i think your SCK needs to be on pin 13 (native SPI SCK).

i did see that, yes, its why i mentioned it :)

@paul can't wait till there will be support for the CS42448 chips, they look promosing (audio channels, bit rate and sample rate wise) for a surround sound decoder or multi output effect pedal. maybe i will change the FX shield i want from 2 sgtl5000 to the CS42448 and add some extra ins and outs.

@paul okay, will adjust the name then :) also, should i go for a single cs42448 with output buffers instead of 2 stgl5000 chips and put some extra inputs/outputs in a seperate header? also, what audio connectors are desire-able? rca, 6mm jack, 3.5mm jack?

FX shield (audio shield for the Teensy 3.6) hi all, i love the teensy and the audio library alot, but since i want a single solution for multiple use cases, i thought: "why not start designing a shield for the teensy 3.6 having all that is needed essentially?" and so i came with the idea of...

for those who want a sketchup file of the teensy 3.6 (not 100% accurate) render:

the average at start was around 84% and now remains over 90% small update, after 1 hour and 45 minutes have passed, the average cpu is about: 91.2% and the peak usage is 91.63% enough updates for now about the usages, it's clear to me that there's a bug somehwere.

the one thing i find weird about it is that the usage stays high and never goes down again even average usage stays high, but still varies a bit, but never gets close to the start value again.

notes: cpu loads are rounded to 1 decimal. start test (peaks: 85.2% cpu, 20 blocks ram) 5 min measurement (peaks: 88.0% cpu, 20 blocks ram) 10 min measurement (peaks: 88.5% cpu, 20 blocks ram) 15 min measurement (peaks: 89.0% cpu, 20 blocks ram) 20 min measurement (peaks: 89.0% cpu, 20 blocks...

hi frank, i will test it for an hour right now, and i never had it with audio projects before the reverb was added in, so it might be that's the issue, i just am not sure yet. anyhow, starting test now with core clock at 120mhz, will respond back soon :) edit: why i suspect the reverb to be...

i don't think so, as the audio memory peak usage is only 17 blocks, with 8 average, so not close to the 30 block i have given it. anyhow, will give it a chance edit: still having the same issue with 60 audio ram blocks (max i tried is 80 blocks (limited by mcu ram), same effect). (measured a...

i am having a weird issue regarding the audio library. namely that the cpu load increases over time. cpu load start: 75.25% after 2 minutes of slow climbing: 80.45% after 5 minutes it has climbed up to 80.87% after 10 minutes it is 81.22% (values are peak) this is a teensy 3.6 with 6 reverb...

hmm.. seemingly my cde had an issue somewhere, i now have the usual speed back :) also anyone has an idea why there is a yield void in the main code?

it switches between 2,5million and 1,2million :s

hm... let me check if i'm doing refresh once or continous refresh EDIT: seems it's not a refresh issue at all!but a issue with how much load there is on the mcu. with a teensy 3.6 and teensyduino 1.31 and arduino 1.6.1 i get about 3 million counts in the main loop a second, where the teensy...

the code running is way slower. it is basically happening with frank's ili9341 library that draws at 4fps at stream mode. i have let him know on github as well.

is it me or is there something major changed since 1.3.1 as i am getting slow screen refreshes after installing the latest 1.8.1 ide and teensy duino 1.35 with the exactly same code?

if there's going to be custom boards, we'll need the bootloader chips to be compatible with the k66 mcu (the pjrc page says it's only up to teensy 3.2)

request for Paul: the datasheet of the k66 family shows me that there is a total of 1mb of flash, with an additional 256KB of FlexNVM for extra program code. maybe make use of that bank of code in the near future?

as far as i know, there is logic built in the teensy 3.6's mcu. but i wonder if those pins are all broken out.

sad thing about spi ram: i can't tell the compiler to look at a specific address to put a huge array of variables (a screenbuffer) in, so i would have to read part of it, do calculations with it, then put it back. aka: slows things down, also the SPI BUS ain't as fast as parallel RAM thanks...

ah darn, but thanks anyway for clearing it up till Paul confirms this.

hey all, i looked at the kinetis k66 datasheets for a brief moment, and found out that it supports a "flex bus" for external memory http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4393.pdf so i am thinking it might be usefull to create a addon board at some point which for...

those are the 'old' ili9163c screesn, as i have multiple of them, and all work with somutoy's ili9163c dma library on a teensy 3.2. haven't tested on a teensy 3.6 yet note regarding the pics: i desoldered the voltage regulator and closed jumper J1 so it works on 3.3V only.

@paul that looks exactly like the ili9163c displays i have, perhaps try that lib? :)

trying to port the video player example for the new lib, it 'works', but i don't have a tft to actually complete my tests if they really work. right now alot is happening code wise, i'm at 240mhz cpu clock and use about 87% cpu while playing the video file (can't get audio to work :S ) i...

your calculation is right, a bit less than 24ms per blend. and yes, the point of overclocking is: to get more performance than default. meaning that if you do some fullscreen blends, you can easily get to 100ms delay time with only one fullscreen blends at 180mhz, leaving alone what other code...

hope you feel better soon, frank! also, seemingly the teensy 3.6 can do a full 240*320px screenblend in < 37ms (you might need to optimize the code for faster speeds) with F_CPU at 240mhz! i created a pull request on github for the demo code. edit: got it down to <18ms per blend (240mhz), will...

hey frank, any update so far? have you seen my github feature request?

perhaps it is a st7735 based controller?

you need to declare the mux::begin void in mux.h as well ;) i just was too quick with posting my answer and am too tired right now to help further, so night. :)

ah, i think i see your problem (it's late here :P) you're making the object with the initializer and are printing a serial message at it. that's not the right way to do it. (initializers can only set/init variables as far as i know) i would do it like this: /* Mux.cpp */ #include...

what are your teensy's usb settings in the arduino ide? (should be serial)

if you're using a teensy, i'd recommend putting a delahy at the begin of your sketch, so your pc has time to set the device up before the serial port opens, i had this several times as well. for example, an arduino uno has a 'startup delay' of about 2000 milliseconds, though i generally go for...

at first i thought you meant something like you wanted a complete media player with touchscreen and nice little gui. but now i opened the topic, i know what you're planning to do. the javascript/html part won't be hard, but to actually be able to do this in the code for the teensy (c++) will...

depends a bit on what your requirmetns are, if you need lots of pixels (like 1280*1024 and above) and need 60fps, then i'd say the teensy 3.6 is even a no-go, as it doesn't have the compute power and features to be able to do that. the fastest i saw was a STM32F4 doing 60fps with some polygons...

sounds really neat, as fat32 can only handle up to 32gb sd cards. keep it up! :)

i am currently trying to write to an 8bit port on my arduino mega, and am trying to translate it back over serial using a teensy. since the teensy 3.2 has 5V tolerance, i wired the pins directly to each oher, and interconnected ground as well. i am getting the right input check of command/data...

i posted a issue on github earlier, with request for a feature, namely HUD overlays seperate from the actual framebuffer. github url: https://github.com/FrankBoesing/ILI9341_t3DMA/issues/9 i started working on this, and i can allocate to a dynamic buffer. only issue i'm having is: how do i...

1: does the teensy 3.6 have an MPU? if so, then i can set it to a specific range, and prevent executing 'protected' flash code (code not in the app api, preventing malicious code to be ran) 2: that won't be that much of a problem, as pebble has their SDK open source, so can start with learning...

bump: does anyone know if this will work with a teensy 3.6 having flash as native flash extention? (if he cpu supports it at all) it's exactly like pebble did it with their smartwatches. if supported: how could we achieve this?

sure thing! also, i might help with some development in the future :)

@frank B i got some example code for slightly more advanced graphical features. (including some AA shapes and somealpha blending stuff) the performance on my teensy 3.2 is rather meh (especially when doing alpha blending for a complete screen of 320*240 @96MHZ), i think because the t3.2...

just wondering if this will work with the ili9341_t3 library?