I did not bring out any special ports. All that was done was SDCARD and USB-PD. But ofc we can keep going and make a gen5 that has more stuff. But it needs coordinating, Rezo and KurtE together could make a full pin mapping, that would be ideal...
So I decided to make a facelift, adding SDCARD and USB-PD which supports the PD protocol up to 12V. There are pads to solder if you just want to use the second port as a pass through with 5V. Meaning, it will deliver the same 5V coming into 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...
Except for the SDRAM added connects as noted in p#926 - the majority of the pins present as a micromod since it is seen as T_MM because of the use of the 16MB Flash. Wonder if anything in the #IFDEF T_MM code might make the difference? Otherwise...
TyCommander can be used as SerMon for multiple Teensys and selectively put them in bootloader (without changing any cores file).
Very handy with more than one online - each can have SerMon display in same or new window.
This works with a Verify...
Made an interesting discovery: it's possible to initialize the SDRAM even before any code gets executed, by filling out a DCD (Device Configuration Data) struct. The ROM processes it and takes care of programming all the SEMC registers when the...
Looking at https://www.pjrc.com/store/ic_mkl02_t4.html
It notes:
10 Blinks = Serial Number Already Assigned A problem occurred with the serial number & ethernet mac address assignment.
Change in CS pin is interesting with changes in TeensyDuino version - but CS usage is normally a live pin.
As for Verbosity, the Preferences page in IDE ( Ctrl+, ) has a checkbox for Verbose compile output and all build info then appears in console.
looking at the TD 1.59 release notes: https://forum.pjrc.com/index.php?threads/teensyduino-1-59-released.74436/
The C++ build moved to #17
Lots of display libs are listed as some changes - some needed changes may have been missed?
Were any...
Running the SDRAM at 270 MHz?
For T_3.6 there was a PCB here wired with resistors to VGA - wonder if it works with the current scheme?
What SDRAM Lib is in use? The one derived from Paul's work on the @mjs513 github or the work @jmarsh did...
@jmarsh - Tested the elcdif sketches. Impressive:D Did not realize the mandelbrot sketch was animated.
Now to hook up the 10.1" LCD and test...
EDIT: By the way the T41 on the breadboard is the first T41 I got from PJRC. It has the white...
First simple experiment on SDRAM board works. Adapted my 4-bit VGA library based on @jmarsh's driver to the dev board. Just had to change two pin defines for FlexIo2 for HSYNC and VSYNC which is used in several places in the FlexIO begin method...
The solder paste used on these boards are high temp 260c, it's actually very good solder. But to get something off you need a good iron and some flux. Or add a little more solder paste from a siringe (the latter is the best and easiest option)...
Hello fellow Teensiers.
First off, this is only for custom boards!
I plan to make the Teensy work with SDRAM. Making custom Teensy boards is something I've done for a while with great success. The forum has been good help and the community we...
In the pic above it is the SPEC below the red squiggle here over the 1062
Not so small if you zoom in :) - next to organic sugar and Kosher salt.
Add flux or put solder blob on solder tip maybe and it should wipe away easily enough and then...
Awesome it arrived and works! V4.0 is the same so far as all else here.
See this post on prior page: https://forum.pjrc.com/index.php?threads/call-to-arms-teensy-sdram-true.73898/post-340933
If you get any SDRAM integrity issues that lone cap...
Just received the sdram development board today:D I ran through all of the test programs that I know about without a problem. I need to make sure I have all of the pinout info for this board. It is a version 4 board.
I thought I would start out...
In the IDE do a Ctrl+T that will do a uniform formatting showing how the compiler might be reading the code.
If all paths are expected to have a return then they should be apparent, if the formatting BREAKS in readability then a semicolon...
'byte RTC_WriteByte(int, byte)' means the function should be returning a byte value.
There is either no return statement before the end of the function, or there is only "return;" with no value, or the function definition should be changed to not...
Starting the IDE it makes a new TMP folder and will build EVERYTHING ... CLEAN.
On subsequent builds then the process will (ideally) not recompile anything that could not have changed where the build results stored in that TMP folder will be used...
Oh - and looking at that warning - do not ignore that!
Was online with @shawn the other month and made a void func() have a return and one path was not covered and got that warning that was not 'SEEN'.
Subsequent builds CRASHED for an 'unknown'...
Is the diff a clean versus a partial build/rebuild?
i.e.: Perhaps the RTC.CPP builds once with warnings and then it is not rebuilt on the next re-build as no dependency changed to cause a rebuild?
Post #7 would be an easy change having the FLUSH done before performing the SD WRITE.
If it still fails, then that is known. If there are no more failures in extended use it fixed/hid the issue. Perhaps it will just add some (measurable)...
re p#6: Rather than memcpy() after data is written to PSRAM perform an arm_dcache_flush() on that region, or pehaps arm_dcache_flush_delete()
This may cause a stall of some duration as the PSRAM data will be flushed to the physical media.
It...
DMA operations bypass the cache on WRITE and also READ. The cache needs proper invalidation.
A: > 'NEW' data values in the CACHE will not be READ/seen by DMA, but the old values on the physical PSRAM will be used.
--> for valid DMA READ the...
If there was only one or two uarts 512 bytes would be fine. But there are 8 ports, two buffers per port that's 8k of RAM which is completely wasted for most applications. That's enough memory that you don't want to just throw it away to make life...
Opps ... These new forum 'partial quotes' "Until Clicked" - I didn't click to expose the rest of the post :(
Seems the rewrite covered the question - hopefully accurately to actual current behavior.
Bummer the pins 24,25 deactivate wasn't found...
Not sure which two pragraphs? If the posted EDIT "To permanently disable this conflict on pin 25 during boot" was just to make clear the only change/issue is during bootloader usage - at 'runtime' there is no issue with pin 25 and it presents no...
This code stops loop() cycling that is stopping the LED cycling.
Rewrite loop() to use a static isPlaying {or GLOBAL as it is} to allow it to start on a button press and monitor the value of playSdWav1.isPlaying() to set it back false when...
Perhaps:
When locked in secure mode, external circuitry which drives pin 25 low can interfere with entry into bootloader mode. To permanently disable this conflict on pin 25 during boot, run this program.
This also stop both pin 24 and 25 from...
On Windows with a sketch open, do a 'Ctrl+K' [open source folder?] will do just that - I did it yesterday for a post ...
If it is an Example - at least on Windows - you can then navigate the installed location.
I have updated the code security page with a "Pin 25 Issue" section and this code. Hopefully it can help everyone in the future who needs to update secure firmware and use pin 25 for input that might be low during boot...
That link presents these steps and now (re)starting IDE 2 doesn't prompt for updates to misc drivers from non-Teensy boards once touched:
Press the Ctrl + Shift + P keyboard shortcut ( Command + Shift + P for macOS users) to open the "Command...
IDE 1.8.19 also has this "Check for updates ..." in the 'Preferences' that isn't on the UI in IDE 2.x
If IDE 2.x has a similar setting under the covers that might stop it from 'looking online'?
Arduino forum might know about that.
And with that...
Worked on similar Locked T_4.1 here - just ran GND==25 :: After uploading this p#17 code
Ouput >> Disable pin 25 during boot
Now on that Locked T_4.1 GND==25 does not affect bootloader upload process.
That also turned off the Pin 24 powering...
Seems as it relates to Locked 1062 it may not be open to change and info limited by secure mode NDA - but this was noted on another thread:
Hopefully the 1062 Teensy pages and the bootloader chip will get notes on Pins 24 and 25 to prevent user...
Not seen any notes about pins 30-31-32.
Just wired 3.3V to them here on a T_4.1 and upload has no issue. Using Blink or SDCARD and ListFiles.ino and SerialEvent.ino noted below.
Something else is going on it seems.
Try this example and from...
Thanks, I'll take a look at it. So far it has been my lack of knowledge of FlexIO and DMA that has slowed me down but I'm starting to understand it more...