defragster
Reaction score
175

Latest activity Postings About

    • defragster
      defragster replied to the thread Help with Teensy Loader.
      Okay - that makes sense. It seems that @luni (?) has made a version that can push .eHex? Someone did (??) - so that could be incorporated into TyComm if so - not sure of @Koromix having bandwidth to do that ... @KurtE has made some builds/edits...
    • defragster
      If Paul suggests that, it would be worth a try to emulate the needed parts of that config function to add that new non-cache region. As I read the startup.c code for the configure_cache() it seemed like altering the cache/MPU when already set...
    • defragster
      defragster replied to the thread Help with Teensy Loader.
      Not sure what this means? TyCommander cannot upload .eHex - it has a Bootloader GUI button that will invoke the Teensy.exe loader program without a physical Button press? Perhaps that is what is desired? A way to have Teensy.exe when not in Auto...
    • defragster
      defragster replied to the thread Help with Teensy Loader.
      Seeing this I went to the Code4Code example done to test on Beta Locking Teensy4 with TD 1.59. Memory Usage on Teensy 4.1: FLASH: code:2959140, data:808368, headers:9000 free for files:4349956 RAM1: variables:179680, code:45864...
    • defragster
      Confirmed. Even with Verify the Teensy.exe grabs/reuses .eHex part #2 when it is missing. But Close and Open Teensy.exe and point to an .eHex with No part #2 and: Still interesting that .eHex part #2 is marginally unique - but any .eHex part...
      • 1708281889907.png
    • defragster
      I believe you have found a previously unknown bug in Teensy Loader. If the 2nd part of .ehex is missing (which never happens when written by teensy_secure), but you previously loaded a good 2-part .ehex file, Teensy Loader ignores the...
    • defragster
      I scanned that partially once following the link - it has expanded since I last looked at it. So, without regard to much of that ... I've built 3 sketches that upload to a LOCKED T_4.1. :: 02:51:42.798 (loader): using encrypted ehex (required -...
    • defragster
      Since the Teensy 3.2 is discontinued I think that I may be able to make some Teensy 3.2 compatible boards to help anyone who needs it. My board will include a LiPo battery charger, Qwiic and USB-C connectors. The price is $25 each. The...
    • defragster
      I finished a prototype and also added a WS2812 RGB LED. The prototype works as I expected. If anyone is interested in manufacturing it please contact me at firebirduino@gmail.com I will give you Gerber files and BOM with 100% open source.
    • defragster
      defragster reacted to mjs513's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
      Finally got the HM01B01 camera working again with Teensy. So hooked it up to the SDRAM board using EXTMEM for the Buffer for still images. Did find that if you hook up a display best to use pins 0/1 for dc/rst if you are using 9/8 for other...
    • defragster
      Perhaps this later in that same thread: https://forum.pjrc.com/index.php?threads/teensyduino-1-52-beta-3.60599/post-238070
    • defragster
      Prior work to assure alignment just over allocated by the alignment bytes needed then set the usable address masked upwards to that alignment boundary - perhaps that is what you did? This 32 byte example from...
    • defragster
      Opps - My bad - the blink is 1 millisecond not a whole second - of course it is not a visible blink. I was taking a quick run with the code and wrongly expecting to see a 1 sec blink like this: void setup() { pinMode(13, OUTPUT); CCM_CLPCR...
    • defragster
      Running this code on T_4.1 or T_4.0 or T_MM not seeing any LED blink? IDE 2.3 with TD 1.59.0 on Win 11
    • defragster
      defragster reacted to Rezo's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
      Here's a quick update from me: Got some 5" and 4.3" LCDs here, 800*480px, 16.7M colors @Dogbone06 sent over some Adaftuit 40 pin lcd breakout boards which arrived on Monday, got to wiring it up day before last, and started testing. Consulted...
    • defragster
      defragster replied to the thread Teensyduino 1.59 Released.
      Updated IDE 2.3 JSON as posted, it was downloaded by IDE Board manager showed 1.59 to update when Teensy was searched. Clicked update and Install completed: It seems to have closed Teensy.exe and nothing else open conflicting prevented...
    • defragster
      defragster replied to the thread Teensyduino 1.59 Beta #6.
      Put a T_3.5 on IDE 2.3 here and it was recognized and uploaded okay - w/tycomm But that WINDOW won't MOVE with title bar? Has NO Title bar - only menu bar on top. IDE is odd? Got that restart dialog again - it only restarted one sketch window...
    • defragster
      defragster replied to the thread Teensyduino 1.59 Beta #6.
      IDE 2.3.0 installed fine and worked for DevBoard build. Seems a good idea with a couple forum installs showing no new issues. Opened 2.1 and got some weird 'something changed restart' - did that twice and close and then the offer for 2.3 stayed...
      • 1707353658721.png
    • defragster
      defragster reacted to mjs513's post in the thread Call to arms | Teensy + SDRAM = true with Like Like.
      @KurtE and I have been testing an OV7670 + spi displays (ili9341 and 9488). While testing the camera using extmem was getting what I would call halo effects: Switching to the pixel buffer in DMAMEM that affect clears up drastically. Maybe...
    • defragster
      defragster replied to the thread Teensy 4.1 psram memtest.
      Yes, that worked on the SDRAM - though had to change clock setting only - resending the IP commands to the SDRAM causes it to lose prior data. That may not apply to the PSRAM as it persists across warm restarts where the full init is already...
    • defragster
      defragster replied to the thread Teensy 4.1 psram memtest.
      That 'fail on write' is actually what I was looking at last on the SDRAM test evolution across speed changes. The PSRAM spec notes a condition where less than the 133 MHz full speed is supported.
    • defragster
      defragster replied to the thread Teensy 4.1 psram memtest.
      Would be interesting if the method of clock speed change details were included and any test sketch that showed the FAIL issue. The speed is limited for a reason since it hasn't been proven/tested good above the current default speed where that...
    • defragster
      Libs installed with the IDE by TeensyDuino or the Boards Manager will be updated.
    • defragster
      Looking at verbose console output this shows for major release build number:
    • defragster
      defragster replied to the thread Teensyduino 1.59 Beta #6.
      Works here: Installed on IDE 2 and Unzipped to IDE 1.8.19 and current sketch built and uploaded for both. Noted above - this is using a new URL: https://www.pjrc.com/teensy/package_teensy_159b6_index.json
      • 1707120405867.png
    • defragster
      We’ve tested a wide range and a narrow range. The results says that 10pF or 12pF is probably the best caps. That’s allot more knowledge then we had before the tests. Further testing is ideally tested by you Paul. My offer stands, there’s a board...
    • defragster
      ... no words ...
    • defragster
      Indeed - was it worth the effort to get toward the CAP detail you asked for? Seemed an important question you had - without this hardware - for some reason. Going beyond the SDRAM 166 MHz has no reason to work reliably. Perhaps some tweaks to...
    • defragster
      Was questioning own results at 3AM so didn't post - but woke up to a better understanding of the one puzzle. At 254 MHz with 13.6 pF hand soldered 5 fixed patterns have no errors and overall errors are 0.0753% so this case is far from 58% errors...
    • defragster
      Mouser order shows 12 pF was 2% and the rest chosen from the @Dogbone06 list shipped 1% parts. The CAP placement/replacement should be easier with Hot Air and much lower temp (<300 instead of >>300) and time on the part should be less with...
    • defragster
      Interesting to see @Dogbone06 - fun that twin PCB design boards somehow diverge on ideal CAP. That Hot Air station on the way for 2/4 - fresh paste 2/5. might give it a try to get matching range of results and do the speed reversion on fail with...
    • defragster
      Just wanted to send a very heartfelt thank you to Paul for building the Teensy 4.1 microcontroller board. The context of this is my team just had our first successful test flight of our 4 tonne drone for fighting forest fires. The entire...
    • defragster
      With the latest code: https://github.com/mjs513/SDRAM_t4/blob/main/examples/CapReadSDRAMTest/CapReadSDRAMTest.ino Testing 3 different capacitors to compare my results to the ones of @defragster. Either his new code is the reason to why I now get...
    • defragster
      One Added Note: Whenever the 'Progress Bar' shows 'a' or "A" it is possible that value failed on Write, meaning #ReRead fails after that on each DWORD tested of the 8M. The Test could .begin() @166 for Write, then Jump to Read test speed to...
    • defragster
      Correct, Until this board went to 13.6 pF (twin 6.8's) 240 MHz always had errors - using the lead solder shown in the images I have done a few runs with 240 MHz and No Errors. <edit> And 'Yes' I plugged posted part numbers into Mouser and got...
    • defragster
      @Dogbone06 - Look for Updated code "CapReadSDRAMTest.ino" - will post again with edit notes to tune the test range if desired. Don't trust the LARGE numbers above/prior - the printf(%u) wasn't bothering with some 64 bit uint added value picked...
    • defragster
      second run 13.6 pF (twin 6.8's) 25 ReReads 240 MHz then 254 MHz: > Error count at 254 here with 13.6 is: 3,662,306 Versus Above 50 ReReads with 10 pF: 540,189,631/2== ~270,094,815 > New 50 ReRead start 227 MHz-288 ... results in some hours...
    • defragster
      @Dogbone06: have you tried going higher than 10 pF - 12 improved here and 13.6 seems even better. Just put two 6.8 pF's on this DevBoard and running at 240 MHz. Test off to best start ever for 240 MHz. It finished - started another run of 240...
      • 1706925705057.png
    • defragster
      @Dogbone06 Here is an extended 50 ReRead Run at 10 pF currently installed - similar to prior. Not seen 240 MHz complete without errors even with 10 pF and the error count is lower when I run 12 pF 10 pF 50 ReReads Mhz Errors % Time Secs...
      • 1706919902128.png
      • 1706919924286.png
    • defragster
      @PaulStoffregen ran again with prec 4 to 8 digits for percentage and with 25 ReReads using 10 pF it shows: Start 57 test with 25 reads 240.00 MHz ... wait::#####e#######AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAA Test result: 4202 read errors...
    • defragster
      Just put a Fresh 10 pF on this original DevBoard and 240 MHz still seems to resolve better with 12 pF at 5 ReReads: 12 pF p#729: 24 read errors {p#272 was: 18 read errors} 10 pF fresh: 933 read errors {similar to prior CAP and soldering} Yes...
    • defragster
      Indeed many millions with dozens or hundreds of errors gives 0.0000% with the precision specified. Doing more tests takes both up in proportion - though sometimes more and some less - each run is its own thing it seems not from a specific value...
    • defragster
      Nothing telling or concrete IIRC. It's been alive almost 5 weeks and that had some quick look and then various diversions (not in build but stand alone lib but with malloc support) and a search for the mystical CAP for higher speeds. Some more...
    • defragster
      No hot air gun here - and solder paste is older so not tried. Odd thing is using iron to remove it often seats better just as it is getting pushed off - not sure if that is too much heat for the cap.
    • defragster
      Very good. Glad the sketch tuned up to work to give you usable results. 10pF sure works better there than it did here before. Did another 12 pF run and it shows more errors on both 240 and 254 than above posted run. I can go back to a fresh 10...
    • defragster
      Dropping from 12 to 11 pF and it shows marginally more errors (.v.s p#279) - so seems higher is better here. Start 57 test with 5 reads 227.37 MHz ... wait::#############............................................ Test result: 0 read errors...
    • defragster
      If you are still at 10 pf change this line from 5 to 25: #define TYPICAL_REREADS 5 Going to 25 did catch some more errors. Then perhaps swap for 12 pF? And put above line back to 5 for a shorter run. Somehow this board got better at 12 pF. I...
    • defragster
      :cool: Not sure what the hang up was (other than SerMon in use)? Using the same code on the DevBoard you sent ??? Indeed, you are having better results and NO ERRORS at 240 MHz Currently using 12 pF here and it improved the 240 MHz and 254 -...
    • defragster
      Opps prior post was based on reading old posts - DOH - but it was UPDATED. Seems like your 2nd Run DevBoard is maybe acting odd? > Wonder if all the CAP resoldering near the MCU edge has affected the Ball solder or gotten flux under it? Those...
    • defragster
      Just updated github with copy here. Using the current version on github there are no restarts and no calls to anything EEPROM.
  • Loading…
  • Loading…
Back
Top