Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: defragster

Search: Search took 0.02 seconds.

  1. Updated the copy of Windows...

    Updated the copy of Windows github.com/Defragster/Tset/ to use this KurtE version - though it is renamed imxrt_size.exe. Using that in 'editor of choice' that can run external batch files to execute...
  2. Looks like it should be usable @Frank - quick...

    Looks like it should be usable @Frank - quick compare is all I can do now … work calls.
  3. @Frank_B it does look interesting - certainly a...

    @Frank_B it does look interesting - certainly a great way to test the concept of alternate linking. I gave the Teensy_4 stuff a quick look - but didn't make the swap when it looked like it might not...
  4. Hi Frank - nice you got the important delivery ...

    Hi Frank - nice you got the important delivery

    Just looking and have not tried the FLASH only .ld. If the .ld file could be changed/selected at build time then alternate versions could go with...
  5. Indeed - I knew I saw FLASHMEM in cores, I didn't...

    Indeed - I knew I saw FLASHMEM in cores, I didn't stop to look how much.

    One extreme case would be alternate LD file that leaves ALL code on Flash unless FASTRUN - that would still use 32KB min -...
  6. Paul has selectively placed some init code in...

    Paul has selectively placed some init code in TEENSY4 tree into FLASHMEM … but that doesn't likely cover some fat things like printf() and other such libraries.
  7. @Frank - with the T4 getting more complete and a...

    @Frank - with the T4 getting more complete and a T_4.1 in the future this may be the time to tune the 'patch everything' things? I assume this refers to defs.h usage providing #define replacements?...
  8. @beermat - something extra affecting this code...

    @beermat - something extra affecting this code ???: libraries direct for devices or printf or other core function use bringing large bits of code into RAM1.

    No reason T4 isn't better on RAM -...
  9. Compile option for RAM_Size or something would be...

    Compile option for RAM_Size or something would be a good way to bypass that with only code in RAM being FASTRUN?
  10. In theory as noted - that is correct. Posted...

    In theory as noted - that is correct.

    Posted results a bit confusing? Minimal shrinkage from moving so much code.

    If FLASHMEM not provided for T_3.6 ( I haven't tried that ) then #ifdef...
  11. @beermat: that is correct. For background look...

    @beermat: that is correct.

    For background look over the Teensy4 info page with the memory layout details - linked in this thread IIRC or www. search for 'pjrc Teensy 4'

    Given that page of info...
  12. Persistent interrupt a pain - but makes sense -...

    Persistent interrupt a pain - but makes sense - it could be polled in loop just as well then.

    When seen in either case - record first time and temp - drop CPU speed or other effort to drop the...
  13. @mjs513 - I passed code you wrote recently that...

    @mjs513 - I passed code you wrote recently that decoded the boot state/history registers already? Maybe you can find that?
  14. I still use it - added it to TSet so it is there...

    I still use it - added it to TSet so it is there on every build as needed for reference - and not tied to TeensyDuino/Arduino install/build. It was updated to match changing T4's 1062 from original...
  15. @Frank - did you see that KurtE updated...

    @Frank - did you see that KurtE updated github.com/KurtE/imxrt-size that you originally made?
  16. Yes that is true, that space is build dependant. ...

    Yes that is true, that space is build dependant. But at runtime when RAM is short the size might be enough to avoid a malloc() of 4 times slower RAM that would end up polluting the DMAMEM/RAM2 cache...
  17. Okay, Here is what I did - added to your code...

    Okay, Here is what I did - added to your code here with call to getFreeITCM():

    #if defined(__IMXRT1062__) // Get Pointer to FREE ITCM
    uint32_t *ptrFreeITCM; // Set to Usable ITCM free RAM...
  18. Good MemInfo Frank. needs line added in...

    Good MemInfo Frank.

    needs line added in setup():

    void setup() {
    while (!Serial && millis() < 4000);
    flexRamInfo();


    I did a sketch that gets the used ITCM boundary and gets a pointer...
  19. Everything is so in paranoid mode {justifiably} -...

    Everything is so in paranoid mode {justifiably} - download an office DOC and it can't run/edit/print without APPROVE.

    I opened the imxtr-size github VS SLN file - and had to APPROVE it to open to...
  20. @KurtE : VS2019 installed - not built - but...

    @KurtE : VS2019 installed - not built - but github debug imxrt-size.exe works now! And back in Sublimetext to compile and build.


    FlexRAM section ITCM+DTCM = 512 KB
    Config : aaaaaaab
    ...
  21. @KurtE - I uninstalled VS2017 weeks back after...

    @KurtE - I uninstalled VS2017 weeks back after 2019 released and you were using it - without install done - and just started - I can't run the imxrt-size.exe from github - your or my old one ...

    ...
  22. 150 MHz Ram2 ( .25 of F_CPU ) - thanks Paul. ...

    150 MHz Ram2 ( .25 of F_CPU ) - thanks Paul.

    Updated my test code - I had addresses printed missing an array dimension in above post - so ignore those.

    I added code for DMA cycle per write test...
  23. Add to p#66 code using: #define DMA_SIZE...

    Add to p#66 code using:


    #define DMA_SIZE 9000
    DMAMEM uint32_t pDMA[3][DMA_SIZE];


    There are some regular MCU cycle waits between 2 and 22 cycles when using that DMAMEM - RAM1 looks to be 2...
  24. Question: RAM1 is CPU speed - what speed is RAM2...

    Question: RAM1 is CPU speed - what speed is RAM2 that it needs to be cached? Some edit to repeat the p#66 ITCM code on DMAMEM blocks could tell me. After posting that code I added another group...
  25. Looks like read and write works there Obviously...

    Looks like read and write works there Obviously on startup the code is written there to fill ITCM with FLASH CODE - this finds that end - skips a word - then writes to next 32K boundary in sketch....
  26. Teensy 3.6 has 256 KB of RAM - the primary RAM1...

    Teensy 3.6 has 256 KB of RAM - the primary RAM1 area of Teensy 4.0 is 512 KB. That is shared with code note marked as PROGMEM. Unless sketch code exceeds 256KB - the T4 will have more memory...
  27. If the pointer math to this is right >>...

    If the pointer math to this is right >> SomeMemPtr

    It is easy to test for the length of >> SizeOfSomeMem

    Of course that memory space is a coincidental amount - that may or may not be 2K or...
  28. Thanks, As soon as I quit for the night I was...

    Thanks, As soon as I quit for the night I was figuring I missed the point of passing the address to memory_copy().

    Given that correction - is that a valid R/W usable RAM pointer (above the CODE)...
  29. Simple sample closer to generic case? Though I...

    Simple sample closer to generic case?

    Though I am getting this output:

    SizeOfSomeMem=15685 [KB=15] SizeLeft_etext=15689 len ITCM=3644801719
    stext=0 _stextload=0 etext=3644801719

    With...
  30. @KurtE, … In the case of :: ITCM : 51600...

    @KurtE, …

    In the case of :: ITCM : 51600 B (78.74% of 64 KB)

    Where the 'next increment of 32KB' : does leave a usable piece of RAM - could that be addressed for R/W usage at runtime?

    In...
  31. Smallest code is just a compilation option at...

    Smallest code is just a compilation option at this point. Rather than exploding code when it would add speed - it tends to reduce resulting code size.

    It might be a future option for Paul to...
  32. For 'Compile DEBUG' output having cryptic stuff...

    For 'Compile DEBUG' output having cryptic stuff can be useful to those looking for it, or for forum debug questions/answers - even with scrolling needed. And those non debug or not interested would...
  33. Speaking of MEMORY - New to CORES on github >> ...

    Speaking of MEMORY - New to CORES on github
    >> avr: pgmspace.h Use DMAMEM for USB serial transmit buffer 12 hours ago
    >> WProgram.h Use DMAMEM for USB serial transmit buffer
    >>...
  34. That is a good (enough) improvement having the...

    That is a good (enough) improvement having the lines not vanish into and pop out of RAM2.



    That would be good if it solves it - Frank B brought this up in Beta as an issue when PROGMEM is...
  35. @KurtE - OP == Original Post Yes, that is the...

    @KurtE - OP == Original Post

    Yes, that is the FLASH copy code to RAM1 as noted.

    After those copes it could set a Global pointer to pFreeFlash for anyone wanting to use the Free Flash area for...
  36. I did a quick scan of the 'Memory Layout' - looks...

    I did a quick scan of the 'Memory Layout' - looks very good. @KurtE - would be good to add to OP if not already done.

    @KurtE - as I understand and from the startup memcopy it seems Any code not...
  37. Using this example:...

    Using this example: "...\hardware\teensy\avr\libraries\Audio\examples\Synthesis\Wavetable\SimpleWavetable\SimpleWavetable.ino"

    It includes this CPP file with no Include of <avr/pgmspace.h>::...
  38. Indeed I just tried variations of all the methods...

    Indeed I just tried variations of all the methods placing PROGMEM found - and they all FAIL
  39. This post:...

    This post: forum.pjrc.com/threads/57459-Errors-quot-not-within-region-DTCM

    Suggests this presentation - not noted if it was effective:
  40. 'RAMming Speed' comes to mind for the FAST...

    'RAMming Speed' comes to mind for the FAST compile - but that wasn't the question.

    For code to FLASH how about :: PROGFLASH
    > of course PROGMEM - was generally to put Data to Flash, but that ship...
  41. Yes, FrankB discovered this during T4_Beta -...

    Yes, FrankB discovered this during T4_Beta - using PROGMEM on DATA and CODE in the same compile unit caused a fail. He tried a counting macro to edit the name progressively and that failed - maybe...
  42. @KurtE - Very good indeed. Amazing how much...

    @KurtE - Very good indeed. Amazing how much added info comes from those few lines of code {after reading your posts :) }! Indeed that info does a great deal to explain the T4's memory.

    I like...
Results 1 to 42 of 42