defragster
Senior Member+

Ick - that was so nice when you undid that ... of course Serial.begin() is optional.

Before I powered up my first Teensy I was looking at DigiSpark 8 bit AVR - a guy there did dithering for gray scale. I don't find signs of it from 6+ years ago ... @MichaelMeissner - any chance you remember that? ...

Not sure if that was crosspost? But the same PCB builds both 3.5 and 3.6 - unless 3.5 was hidden under the big USB CAP - all else is common.

That is a T_3.6. Reason: The T_3.5 and T_3.6 share the exact same PCB. Differences are: MCU Marked as MK66 on that T_3.6 picture and the T_3.5 would have an MK64. Also on that the row of 5 inner pin holes...

Not having used the library - but again charlieplexing works by running (fast cycling) power out the desired pins counting on the diode to light when biased properly and block otherwise. RE p#6 :: At no point...

Three pins - at any one time one is GND and at most two on a row are HIGH? wiring not shown - and just guessing from general understanding and quick wiki glance ... 5 and 6 are on a row and powering them uses pin 4...

Okay, thought maybe you had the math and logic to find and walk back the call stack. Frank has the PR to PJRC CORES for his code and I put a PR on hit PowerButton with an updated copy of the hardfaults.cpp that...

No interrupt disable! I should try looking at the Teensy3 code ( that does disable ) to replace when over 48 MHZ ( exclude T_LC with no CYCCNT and slow speed issue ? - but ould require CYCNT - and not having user using...

Cool! - you got it working Single 32 word is to be atomic - says Paul - is lastCurrent not a single 32 bit DWORD word ... from a single DWORD? Maybe it changes between READ and Assignment? If you ever have issues...

Found this newer post that may work as a faster example: Teensy-4-0-PORT-manipulation-to-read-write-data-to-multiple-pins Shows port read from ordered pins and masking to get the value. Post #9 there noted it takes...

There is this page with a sample sketch that should run and provide a table of the PIN to PORT mapping :: TeensyUser/doc/wiki/Mapping-Pins-to-Ports Look around there perhaps for port read usage? I didn't see it...

Follow the links in this post - one should demo a port read of all the pins on that port :: Teensy-4-1-8-Bit-Parallel-I-O That post is from mid 2020 - there may be other newer posts but IIRC at least one demonstrated...

Quick single search shows it here : www.math.sci.hiroshima-u.ac.jp/m-mat/MT/TINYMT/index.html URL the same - just a ~ changed in the path. On github as : github.com/MersenneTwister-Lab/TinyMT > last update : Aug...

Good luck with whatever is working to trace back. If you have code that can walk back and uncover the stack in any way please post. The code edit just forwarded to FrankB could capture that onto PSRAM or RAM2...

That would be this then :: effective states : -1 (when REV held) or 0 or +1 (when FWD held) The code posted has a lot more involved that isn't relevant given no analog is desired ... Perhaps start with this...

Since it wasn't stated ... had to ask given the use of 5V - could have been an AVR Teensy - otherwise it makes no sense to use 5V for an input when while 5V tolerant - it is a device designed for 3.3V usage. Any pin...

I'm using p#522 here - just minor tweaks for cleaner output and a KurtE Edit that works between 506 and 507.

What Teensy is in use? Is it one that is 5V tolerant? From 2 buttons FWD and REV ? Is the motion to stop when the button released - not return to zero?

Looking at the T_3.5 card. The Compact notations there indicate:: For WIRE - bold is default pin and non-bold is alternate for selection using .setXXX() to use the Alternate pins pin: function 19 : SCL0 18 :...

Was there a change I missed for improved SD card reading? I have four partitions on mine and it is only giving this: Initialize SD card...SD card is present. SD Fat Type: Fat32 Volume Name: SD1_8GB_AD done......

FrankB's code isn't in a PJRC release yet - just a Pull Request on github. I made some edits for his review that allows call to user sketch on a FAULT to save data to DMAMEM or EXTMEM for view after restart. This...

The Bootloader responds to the button by a hardware signal on the board. The USB Wire signal requires a functional USB Stack. Having output is one thing that somehow often works. But the USB jump to Bootloader...

@MeBoop: Writing to the SD in faulted state is suspect? Lots of overhead and moving parts have to be working for that? As noted - some faults allow USB Serial.print() others do not - but returning from fault handler...

@MeBoop - indeed - would be great to see your 'crash trace dumo' code. FrankB added a great T_4.x solution using the RAM2 area for Fault data storage. RAM2 is not zeroed on restart and if power is maintained that...

Looks right for FAT32. Fat16 was big enough for MS-DOS as HDD's grew - much more so accounting for var sized clusters with compression factor of 16:1. Even Win95 with FAT32 couldn't fit FAT in single alloc limit of...

p#523 crosspost ... Windows view of USB Hub Drive >> H: << and Flash drives >> F: and G: << as below: Here is run on p#522 updated code - now has ExFat drive size: Waiting up to 5 seconds for USB drive 1...

Just plugged in my 5 TB external - yesterday's code - doesn't matter given the part ID #238: msc # Partition Table part,boot,bgnCHS,type,endCHS,start,length...

Great! Also easy to use :: #define WIRE WIRE2 Not sure where those pin numbers came from they don't seem to match any 32 bit Teensy card. The T_3.5 and 3.6 can use ALT WIRE on pins 7&8.

The T_4.1 package is : LFBGA196 and 12 x 12 mm, 0.8 mm pitch, ball matrix The 1170 package is : LFBGA289 and 14 mm x 14 mm, 0.8 mm pitch There was a note IIRC the board would have to be bigger just to hold the...

As noted those pins are for Wire2 So all the WIRE commands need to use WIRE2 not WIRE That should select the right internal hardware to connect those pins.

Glad you got it - there is an #if 0 in setup that will quickly confirm Faults are trapped as configured. Locked up? Does it do the CARAT printing from timer with "#define SHOW_CLOCK_CARAT 1"? If not then it is...

@wwatson - perhaps with line #16 on in UPDATE sketch below : //#define SHOW_CLOCK_CARAT 1 That will show MCU running but USB msgs stalled. Have you hacked in the PR for HardFaults just to know if any hang results from...

Fun News: Fresh 128GB SD - as noted with 116GB primary ExFat. Week old Windows 10 i7 - running next release of Windows 21H1 insider build: On SD Deleted Factory Partition - Created one of 8GB { after format : BSOD...

p#494 sketch looks Great! Grabbed a fresh 128GB SD card and will make it Multi Partition. I thought to do something like procesMSDrive(1, msDrive1, msc1); rather than Dupe - but time was limited and wanted to get...

Buying a Teensy LC would have least cost - especially if you really use 5 of them. Not sure of any reason it wouldn't work as well as the others for this dedicated purpose? See this for PCB creation and DEMO:...

Done for now - Got Twin Drives Hacked in and working!!!! Duplicated setup code for msDrive 1 and 2 in loop() - and pass ptr to msc1 or msc2 to the func( UsbFs *myMsc )'s that need it ( mbrDump and volLabel()'s ) >>...

GOOD NEWS! Looks like it was used a year ago for USBHost testing. Now it just needs to be coded to bring up a second drive as well. My 120GB HUB DRIVE is ExFat and now works - seems to have Vol Label - and it...

Turned on USB DEBUG This is the inital case on power up where ExFat works: new_Pipe new_Pipe Descriptor 5 = ENDPOINT Descriptor 5 = ENDPOINT Initialize USB drive...control CallbackIn (msController) 00 00 00...

Put the Teensy MSC formatted ExFat drive on Windows - looks good. Had 16 MB Unallocated before the ExFat Partition. Made that space into a FAT drive. Both Volumes have usable names - NOT SHOWN, and it sees the...

Code Merged - ExFat 128GB Flash lives: Waiting up to 5 seconds for USB drive ^^^^Initialize USB drive...^^^^^~USB drive 1 is present. msc1 Partition Table part,boot,bgnCHS,type,endCHS,start,length exFAT:...

Argh - that p#479 doesn't have my edits in :( I have another drive : Flash 128 GB that was seen to FAIL using to backup PC data. I just went to MSC ExFatFormatter - here is Format okay and startup okay ... then...

Turns out BOTH of these drives are MSFT formatted :) One for recover 64GB with 2nd partition now formatted where they image it with one of 32GB The second 16GB drive they format when putting on the WIN 10 install...

Just made this ehci.cpp change to my system - No change to (1) on the startup Hang with write protected drive: USBHS_USBCMD = USBHS_USBCMD_ITC(1) | USBHS_USBCMD_RS | This system has HardFault detection enabled -...

Just back ... 'not Working' is the norm ... didn't read enough of the thread :) > this with minimal USB 2.0 'hub' - not powered Updated above post #470 :: That is how Windows sees it, MSFT formatted it when they...

TyCommnader finds all online Teensy units. When part of the build process it pops up a dialog to 'pick your Teensy' the first time that hex is uploaded - then on subsequent uploads of that hex it is associated with...

... first pass answers links to other info ... Forum search for ILI9488 will find development and notes on SPI display usage. There are options for continuous DMA update or single write processing and the screen can...

... using the p#469 code { I added : >>>pt->type: 12 } My favorite/most used Flash is a FAT32 16GB with a physical write protect switch. That is how Windows sees it, MSFT formatted it when they put on a Win 10...

Always a pain to plan soldering in advance for pin or socket and top or bottom - and picking the wrong combo leaves a hassle to deal with :( If properly wired - and the jumpers are well connected - the jumper type...

T_4.1 with KurtE code ( and the p#467 Volume Name edit ) - on unpowered hub just the two partition 64GB Flash works! >> NOTE: putting this flash in Win machine mounts both partitions/drive letters also. Pulled SD card...

Using unpowered Hub and the 64GB Flash with 32 GB recovery Part - the 2nd part shows using KurtE code: Notes on output below: > there are about 300-400 pages of files displayed in TyComm on the recovery drive - does...

Some hacking here - esp with my odd powered hub that has internal device #1 of a 120GB HDD - then as coded it doesn't look beyond msDrive1. Also odd about the hub as before - once enabled the Hub/HDD backfeeds power...

PR prepped to update with latest and LFSIntegrity got pulled into PJRC tree. Copied those files to git.defragster\lfsintegrity so they match now for changes going forward.

Finally built here ... swapped PJRC git USBHost into sketchbook/libraries ... still fail Deleted that to use the td1.54b7 installed copy and IT BUILDS! { Maybe re-using the sketchbook folder left some debris? } ...

This was pulled for use :: github.com/KurtE/USBHost_t36 >> "This branch is even with PaulStoffregen:master."

Odd ... Maybe https://sectigo.com/cps-repository hasn't reported the cert details to MSFT yet? I see these unfilled filed looking at the exe?:

tCode is my sketchbook folder for local installed libs to replace any other installed libs. This is where I dumped the downloaded ZIPS from the github pages. Used: T:\tCode\libraries\USBHost_t36 Not used:...

Awesome. Let me know if anything changes - the git.LFSIntegrity should match? We can manage any updates but that helps formatUnused look useful and improves/updates LFSIntegrity.ino.

The list of LIBS used looked right ? Unless I have an old copy? Seeing this makes it seem like a prototype is missing from ??? T:\tCode\libraries\USBHost_t36\MTPDevice.cpp:318:6: error: 'MTPDevice' has not been...

YAY for you :mad: - what am I missing :(

Just poking at the downloaded EXE I got to a dialog - Install Certificate on Machine (versus user) ... Hit the download again and - same grief. So the SmartScreen doesn't seem to ask the machine if the cert is...

That is a hack that doesn't help the desc.h issue. It came up a beta or so back and it handy. Anything there adds to or overrides anything in the base boards.txt. Offline about now - will look for USBHost/MSC/MTP...

@mjs513 - if these lines are in this file (thanks FrankB) : ...\hardware\teensy\avr\boards.local.txt teensy41.menu.usb.mtpserial=MTP Disk Serial (Experimental)...

That 'verbose info looks like the linker output as it parses the ELF with this line added to build.txt? ## teensy41.build.flags.ld=-Wl,--print-memory-usage,--gc-sections,--relax "-T{build.core.path}/imxrt1062_t41.ld"...

I also reported the download site as safe again in the process. There was a pre release test version I did that on as well the other day - and did that again this time when I tested to see if that version might be...

@Paul - for reference on this new Win 10 machine that doesn't like the NEW 2021 certificate I just downloaded this file with NO WARNING from browser or the system or BLOCKING - even the EXE runs without 'UNBLOCK' with...

All seems well with the Beta 7 - ran the IDE some to good effect. Then back to in editor command line and all is well. re #1 :: Teensy.exe cycling between 0.0%. 0.1% and rare 0.2% of CPU usage on Windows 10...

@mjs513 ... Made a github.com/PaulStoffregen/LittleFS/pull/8 to update from this fork: github.com/Defragster/LittleFS

@mjs513 ... TD 1.54 b7 came out with OLD LittleFS in place. Is the current github.com/Defragster/LFSintegrity up to date for a complete pull to PJRC github.com/PaulStoffregen/LittleFS I need to put it back here...

Opps - that explains the change after new install. So now back to the errors in post #438 from that posted code ? T:\tCode\libraries\USBHost_t36\MTPDevice.cpp:318:6: error: 'MTPDevice' has not been declared void...

Installed TD 1.54 b7 and build changed. Compiled SERIAL, MTP DISK ( Experimental ) , MTP DISK SERIAL ( Experimental ) This is for : MTP DISK SERIAL:: Detecting libraries used......

This new up to date Win 10 Pro machine gave this clicking the '...': Keep ... Then it gave this after clicking the '^' option carat: Keep Anyway ... Then this usual prompt because I had not done 'Properties...

Thanks, that was the link I forgot - though I had downloaded it yesterday I see. Busy week downloading on New Computer setup - over 30 things in there ... Looks like some mystery ... sketch from post #433 fails big...

Haven't poked here for some time - now more involved parts collection: github.com/KurtE/USBHost_t36 :: Even with Pauls' and no edits github.com/KurtE/MTP_t4/tree/MEM_send_object_large :: 23 hrs old ... and some...

@all : new images of the updated T_4.1 is online :: pjrc.com/store/teensy41.html#pins

Yes - see : store/teensy41.html#pins That shows the Arduino pin numbers for the SDIO pins

Hoping to catch up with this soon - USBHost , MTP, MSC ... will have to find the current common sources and stop being distracted by life and new computer setup.

Just put a note on Frank_B's PR Print Hardfaults #535 - that would be good to have in Beta 7 release so a thread could be started to discuss and put it to use on T_4.x's. @KurtE - 4K bump was in the error detection...

Following p#85 shown above. It looks like RAM calc goes in 4K chunks? Not a code multiply but from ?? :: "data = elf_section_size(".data");" Using this for RAM is too much - like anything higher than 464 :: char...

If you over alloc in an OBVIOUS way - or even barely: The build breaks in ld.exe before getting to run the teensy_size.exe: ...

PR updated for only resources in Error to show in console COLOR. github.com/Defragster/teensy_size/blob/patch-1/teensy_size.c

Did PR to have ERRORS get highlighted in console: char *prefix = "teensy_size: "; if ((free_flash < 0) || (free_for_local <= 0) || (free_for_malloc < 0)) { retval = -1; prefix = ""; } Would be...

When there is an error to result in a '-1' exit - the text "teensy_size: " should NOT be printed on the Error line so it gets proper color coding.

Quirks indeed ... It was noticed in beta IIRC that there was LARGE timing asymmetry in I/O value changes. That seemed to go away - or at least not be super extreme - perhaps that was early when I/O went from 'slow'...

And for mtp-test - looks good?: teensy_size: Memory Usage on Teensy 4.1: teensy_size: FLASH: code:140560, data:13176, headers:7212 free for files:7965516 teensy_size: RAM1: code:163840, variables:37696 ...

Still looks good. this shows here? Maybe just a local issue - but %lld fixes it. teensy_size.c:54:43: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'size_t' {aka 'long long...

Well everyone should use Verbose mode. For those using non verbose wasn't expecting this detail to be ejected. But if the normal output gets clipped then that won't show for non-verbose ... Opps Though making it...

Good to know - so that is (current) 'fixed' MCU overhead - not something user code will affect - but takes space on the FLASH.

@FrankB - thanks for the EXE! LFSIntegrity shows this when added to TSET cmdline build - when using EXTMEM char buf RAM LFS Media: FLASH: code:86092, data:10160, headers:7212 free for files:8023000 RAM1:...