Search results

Thanks @jmarsh and @mjs513 Quick note on the main CSI pins, (AD_B1_xx) pins, that are used on Teensy 4.1. They are also FlexIO pins but on FlexIO3, which does not have DMA, so we have not tried using it... But could especially, if we do it without DMA anyway... Was first experimenting today...

Wondering has anyone tried using the CSI subsystem without using their built in DMA? Two different ways, I might find it interesting: a) Reading in JPEG. Yesterday I was sort of able to get it to maybe read in one JPEG using DMA, I think I have that part broken a bit right now as was trying...

I think which new pins could/should be added to support has been shown now in a few threads including: Question, what do you mean by complete? That is I have not seen what I would consider a complete one for DB4 or DB4.5. That is one that shows all of the signals for EMC and now SDIO. Is...

I could not tell from your description, if there is a common GND signal? That is does your USB GND connect to the Teensy? Edit: sounds like there is, but would double check... (I was thinking of a different thread....) But Pictures of your setup might help. For example, to show you are using...

Quick updates on CSI code: I now have more of it working with T4.1 and CSI running in VGA size, with PSRAM for frame buffer. I have more of it working now. With the VGA sketch, using OV7675 camera PSRAM, where f command is working, as is m and F... Next up try to setup with one of the...

Sorry, I did not go all the way up on the SS to those pins... I have now... Exactly. Pushed up current version to fork of defragsters github project and issued PR https://github.com/Defragster/EVKB_1060/pull/1

Thanks, @mjs513 (and others), I updated again the dogbone... excel document all of the LCD pins on the right hand side of the board were filled in. I think it should look like: Will send the document back to you and/or could try to do PR with it back to @defragster and/or could put it up in...

True, I have not really studied the LCDIF as I don't think we have had any boards that have enough pins exported to use. I might take a look and see if we added the 3 or 5 pins mentioned in yesterdays post about CSI... If both would be covered or not.... Other side note: I am currently playing...

Looks like the method: int vprintf(const char *format, va_list ap) { return vdprintf((int)this, format, ap); } Was added last year (May 2023) Wonder if they should have not put the implementation of it within print.h but instead into print.cpp, where there are two other methods implemented that...

I wonder if there are any hints on this on how they use SDRAM with CSI in the 1050 document https://www.nxp.com/docs/en/application-note/AN12110.pdf

@mjs513, looks interesting. Wonder what the differences are from the DMA and non-dma? Other than the obvious. Like when we are not using DMA operation, the new data is written to the cache, and only later, when necessary, it flushes it out to the real memory. But with DMA we are writing...

I slightly updated @mjs513 copy of it he sent recently. In that I filled in more information about the newer pins I Hid most of the columns, which shows: The ones in Yellow are the ones we do not have. 3 are critical for CSI (D3-D5) The PIXLK/MCLK - There are currently other pins on the...

As for the Teensy 4.1, I am using a board, I made maybe 4 years ago, and the one I am using is not fully populated. Don't remember if I assembled any others of that batch and if so what parts worked or did not work... The board is more or less same size as the 2.8" ILI9341 display, As I...

Note: no promises on these boards, as I am a retired software guy.... I was laying out a complete board as a modified version of the earlier board I did for the Micromod. But decided to do a quick and dirty one that I can easily solder up. So this one simply plugs into a Sparkfun Micromod ATP...

Thought I would mention, I am currently playing with trying to add CSI support for this library, as the Teensy 4.1 has enough of the CSI pins exposed for 8-bit transfers, and the control signals. I am starting off with the OV7675 camera, and I do have it now being able to display a QVGA image...

Sorry been awhile since I played with the joystick stuff. Most of my playing has been done on the USB Host side. There are at least three things to do to see if it works. a) Update the HID descriptor. It may or may not be as easy as removing items. That is there are some types of fields...

Note: that is simply a print to pdf of one of the pages in the excel document: https://github.com/KurtE/TeensyDocuments/blob/master/Teensy4x%20Pins.xlsx Note: @mjs513 did a modified version of this that I think is in @defragster github project: https://github.com/Defragster/EVKB_1060/tree/main/docs

If you are building a specific board for a specific purpose, I say have at it! IF you like hard coding it like: IOMUXC_SW_MUX_CTL_PAD_GPIO_AD_B1_13 = 0x4U; IOMUXC_CSI_DATA04_SELECT_INPUT = 0; IOMUXC_SW_PAD_CTL_PAD_GPIO_AD_B1_13 = 0x0U, go for it. This could be fine for CSI where for there are...

Yes you are right that B1_12-15 are already on the board. We should probably make a new version of the excel document which has all of these pins on it... As for mixing CSI and FlexIO. Not sure how... Probably need to read those sections in the PDF a few more times (like 10 or 20) to try to...

@mjs513 did the one for the devboard that I am looking at. Looks like most of the pins are there. We are currently using AD_B1_04 through AD_B1_15 Mike does the below look correct to you as well? The T4.1 defines we were using.. The numbers at start are I believe on this board with pin...

Works for me, with the Devboard, as I created a variant that had all of the extra pins defined. Otherwise you would not have pin numbers to work with... True, typo...

A couple of questions and things I am playing with... With the 4.5 and SD adapter: guessing you used SDIO pins? (Same ones as defined for Micromod?) of if SPI which IO pins? CSI pins - I am in the process of integrating in some CSI support into the library that @mjs513 and myself have been...

Just wondering, are you saying that on the current Devboard 4, that the 3.3v Voltage regulator is maybe to anemic to run some of the different devices that you have connected to it? And that maybe we should add another one to connect the devices, such as displays and cameras to? Hopefully the...

Thanks @mjs513, As you mentioned we are having some fun with several of these cameras. I see you showed my quick and dirty (v2) version of a shield for the Sparkfun Micrmod ATP board. Sure is a lot easier than having to deal with lots of different jumper wires and the like. Sort of turned...

It is up to your sketch to define the mapping. If you look at the example joystick complete example you see code like: for (int i=0; i<numButtons; i++) { if (digitalRead(i)) { // when a pin reads high, the button is not pressed // the pullup resistor creates the "on" signal...

Sorry been long time since I did much with these displays. Most of this should work the same way as our other drivers... It may depend on what you mean by size. That is not every character has the width and the like: Most are proportional fonts. Note: the ILI fonts are structures, which is...

Me too. But it was in his first line, which my eyes missed on the first readings.

It runs on mine, using recent nightly build and current Teensyduino... Using library ILI9341_t3 at version 1.0 in folder: C:\Users\kurte\AppData\Local\Arduino15\packages\teensy\hardware\avr\1.59.0\libraries\ILI9341_t3 However I edited to my boards CS, DC, Reset pins. Not sure with your setup...

Yep - but I also played with the beta releases 😆 Believe me, I know the feeling! Actually mine is set up to use the Windows Terminal, which I like a lot better!

Newer versions of Windows? Like maybe only the last 30 years :LOL: Maybe longer... I am guessing that a large percentage of users on Windows (and probably MAC) almost never have used a command line. So, things like Folders are a lot easier to visualize than directory... Git/Github - Yes the...

Or use a 🔨 😉 Not sure what temperature solder that was used. Mine was a bit stubborn coming off, so I partially cut it off...

Sorry did not have time today to fully diagnose the issue. But I dos see some issues with the code, although I would think you would still see something. int buffer0[100]; int buffer1[100]; int buffer2[100]; int rxdNum[1]; int rxd1Num[1]; int rxd2Num[1]; ... rxdNum[0] = rxd.toInt()...

Couple of different ways: For example: several of our display drivers have code built into them to allow them to do asynchronous updates. Like my ili9341_t3n library as well as others for ST7735 and ST7789, and ILI9488_t3n library. In these libraries we have code that uses the DMAChannel...

What happens if you change: ILI9488_t3 screen = *new ILI9488_t3(CS_PIN, DC_PIN, RST_PIN, MOSI_PIN, SCK_PIN, MISO_PIN); to simply: ILI9488_t3 screen(CS_PIN, DC_PIN, RST_PIN, MOSI_PIN, SCK_PIN, MISO_PIN); And not create it using the new operator...

This latest one appears to work... Got the two messages that Defragter mentioned and then: And ran from terminal window and it worked

Sorry, again at least for me it is really hard to tell. The only thing that Arduino 1.0.5 tells me, was it was done a long time ago. A more meaningful indicator might be what version of Teensyduino, but not by much. The USB types are part of the Teensy install... At a higher level, you...

Sorry, I am pretty sure there will likely not be support to run on Arduino 1.0.5 with any version of Teensyduino that supports the Teensy 4.x boards. Sorry. I personally have no idea what the Real Time System Custom USB is or was? Maybe others do? So if possible you may want to post more...

Should work

It would probably be a good thing to do. But not sure how many sketches would be hit that include both SD.h and SdFat.h... But would probably be worth a try.

Again not much one can do, without more code, but one thing I noticed: void PlayMode::myNoteOn(byte channel, byte note, byte velocity) { if (synth != nullptr) { synth->oscPlay(40); } } void PlayMode::myNoteOff(byte channel, byte note, byte velocity) {...

Microsoft windows, complained twice as mentioned. Then Norton ran on it and said something like, scanned, ... But I think there is a bug in it: C:\Users\kurte\Downloads>hello3 Hello Defragster As I am not Defragster 😉

The one main complication you might run into, is what if you wish to build some sketches for other Arduinos that use SdFat. They will not find the libraries that are installed within the Teensy Board installs. If you install the normal official SdFat library, then it breaks the Teensy...

Norton complained about 3 times about not a common download, Are you sure... But after that I was able to run it. Norton also scanned it and said nothing is wrong.

I know the USB Host code can tell keyboards the logical state of these through the LEDS( code, which sends out a control packet: driver_[0]->sendControlPacket(0x21, 9, 0x200, 0, sizeof(leds_.byte), (void*) &leds_.byte); Not sure if we listen to it on the USB Device side... looks like we keep...

In the case of the ATP, I believe that this is due to the Voltage Regulator they choose for the board. AP7361C states: Wide Input Voltage Range: 2.2V – 6.0V And yes if you build your own board, with different VR or DC to DC converter, you can change it to what works... Like maybe /4 more...

Not sure, but most of their carrier boards, have something like: That is from their ATP board schematic. As for AREF, don't see that on their stuff. With Teensy it is probably geared more to the 3.3v pin. I don't believe raw VIN is passed to the Micromod connector. For me the pin had issues...

Note for things like this, I end up using sketcth that @defragster and I played with a long while ago: It sets all of the pins into either INPUT_PULLUP or INPUT_PULLDOWN. You can then take a jumper wire from either GND or 3.3v depending on which mode you are in, and touch each pin. It will...

Funy you should mention it... I believe one or more of the pages has the ATP pins on them as well... I just so happens, as I mentioned up on the thread about fancy memory :lol: I decided to make a quick and dirty shield for the ATP board, which I ordered a set from OSHPark... @mjs513 can...

I believe that you need to update the USB descriptor to have JOYSTICK_SIZE=64, which then gives you things like: #elif JOYSTICK_SIZE == 64 void button(unsigned int num, bool val) { if (--num >= 128) return; uint32_t *p = usb_joystick_data + (num >> 5); num &= 0x1F...

Sorry, I don't know how your image is created and/or stored. The sketch you mention only supports specific format bitmaps Does your run give you additional information, like why it did not like the file? Not sure what you are trying to do, as you mention your display is something like an...