Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 13 of 13

Thread: Teensey Loader Problems

  1. #1
    Junior Member
    Join Date
    May 2021
    Posts
    17

    Teensey Loader Problems

    Hi,
    I have been having problems loading new code onto my Teensey 4.1. I have tried several different sample programs and 2 known/working usb cables.

    The log from a verbose snapshot from the loader( Version 1.55) is below. I get the same behavior even when compiling/loading the basic blink program? What is going wrong? I have used this board before and it was recently sitting for a couple of months. The board worked before/is genuine.

    In the log below.. I see the line "23:31:18.259 (loader): Opps, NXP ROM in open mode, but we do not yet have code for this case "

    What does this mean, how do I close the NXP ROM, I assume that has something to do with the problem I am having.

    Note, when I press the load button on the Teensey 4.1 , I get messages on the log below/activity, proving that the cable is good, but an anomaly is encountered.


    23:29:50.709 (loader): file changed
    23:29:50.727 (loader): File "C:\Users\Jeffrey\AppData\Local\Temp\arduino_build _195947\Example2_OutputToProcessing.ino.hex", 33792 bytes
    23:29:50.730 (loader): File "Example2_OutputToProcessing.ino.hex". 33792 bytes
    23:29:50.733 (post_compile 3): Begin, version=1.55, high-res time
    23:29:50.740 (loader): remote connection 11120 opened
    23:29:50.742 (loader): remote cmd from 11120: "comment: Teensyduino 1.55 - WINDOWS (teensy_post_compile)"
    23:29:50.742 (post_compile 3): Sending command: comment: Teensyduino 1.55 - WINDOWS (teensy_post_compile)
    23:29:50.743 (loader): remote cmd from 11120: "status"
    23:29:50.751 (post_compile 3): Status: 1, 0, 0, 14, 0, 0, C:\Users\Jeffrey\AppData\Local\Temp\arduino_build_ 195947\, Example2_OutputToProcessing.ino.hex
    23:29:50.751 (post_compile 3): Sending command: dir:C:\Users\Jeffrey\AppData\Local\Temp\arduino_bu ild_195947\
    23:29:50.752 (loader): remote cmd from 11120: "dir:C:\Users\Jeffrey\AppData\Local\Temp\arduino_b uild_195947\"
    23:29:50.754 (loader): remote cmd from 11120: "file:Example2_OutputToProcessing.ino.hex"
    23:29:50.755 (post_compile 3): Sending command: file:Example2_OutputToProcessing.ino.hex
    23:29:50.768 (loader): File "C:\Users\Jeffrey\AppData\Local\Temp\arduino_build _195947\Example2_OutputToProcessing.ino.hex", 33792 bytes
    23:29:50.770 (loader): File "Example2_OutputToProcessing.ino.hex". 33792 bytes
    23:29:50.774 (loader): remote cmd from 11120: "status"
    23:29:50.782 (post_compile 3): Status: 1, 0, 0, 14, 0, 0, C:\Users\Jeffrey\AppData\Local\Temp\arduino_build_ 195947\, Example2_OutputToProcessing.ino.hex
    23:29:50.782 (post_compile 3): Sending command: auton
    23:29:50.782 (loader): remote cmd from 11120: "auton"
    23:29:50.784 (post_compile 3): Disconnect
    23:29:50.807 (loader): remote connection 11120 closed
    23:29:51.138 (post_compile 4): Begin, version=1.55, high-res time
    23:29:51.140 (loader): remote connection 11124 opened
    23:29:51.143 (loader): remote cmd from 11124: "comment: Teensyduino 1.55 - WINDOWS (teensy_post_compile)"
    23:29:51.144 (post_compile 4): Sending command: comment: Teensyduino 1.55 - WINDOWS (teensy_post_compile)
    23:29:51.146 (loader): remote cmd from 11124: "status"
    23:29:51.155 (loader): remote cmd from 11124: "dir:C:\Users\Jeffrey\AppData\Local\Temp\arduino_b uild_195947\"
    23:29:51.156 (post_compile 4): Status: 1, 1, 0, 14, 0, 0, C:\Users\Jeffrey\AppData\Local\Temp\arduino_build_ 195947\, Example2_OutputToProcessing.ino.hex
    23:29:51.156 (post_compile 4): Sending command: dir:C:\Users\Jeffrey\AppData\Local\Temp\arduino_bu ild_195947\
    23:29:51.158 (loader): remote cmd from 11124: "file:Example2_OutputToProcessing.ino.hex"
    23:29:51.159 (post_compile 4): Sending command: file:Example2_OutputToProcessing.ino.hex
    23:29:51.172 (loader): File "C:\Users\Jeffrey\AppData\Local\Temp\arduino_build _195947\Example2_OutputToProcessing.ino.hex", 33792 bytes
    23:29:51.176 (loader): File "Example2_OutputToProcessing.ino.hex". 33792 bytes
    23:29:51.183 (loader): remote cmd from 11124: "status"
    23:29:51.193 (post_compile 4): Status: 1, 1, 0, 14, 0, 0, C:\Users\Jeffrey\AppData\Local\Temp\arduino_build_ 195947\, Example2_OutputToProcessing.ino.hex
    23:29:51.193 (post_compile 4): Disconnect
    23:29:51.210 (post_compile 5): Running teensy_reboot: "C:\Program Files (x86)\Arduino\hardware\teensy\..\tools\teensy_rebo ot.exe" teensy_reboot.exe "-board=TEENSY41" "-port=fake serial" "-portlabel=(null)" "-portprotocol=(null)"
    23:29:51.215 (loader): remote connection 11124 closed
    23:29:51.225 (loader): remote connection 11124 opened
    23:29:51.252 (reboot 6): Begin, version=1.55, high-res time
    23:29:51.252 (reboot 6): location = fake serial
    23:29:51.252 (reboot 6): portprotocol = (null)
    23:29:51.252 (reboot 6): portlabel = (null)
    23:29:51.252 (reboot 6): Emulated serial devices will be tried first
    23:29:51.252 (reboot 6): LoadLibrary cfgmgr32 ok
    23:29:51.252 (reboot 6): LoadLibrary ntdll ok
    23:29:51.254 (reboot 6): nothing new, skipping HID & Ports enum
    23:29:51.258 (loader): remote connection 11128 opened
    23:29:51.264 (reboot 6): Disconnect
    23:29:51.289 (loader): remote connection 11128 closed
    23:29:51.296 (loader): remote connection 11124 closed







    <After Button Press>



    23:31:17.864 (ports 2): WM_DEVICECHANGE DBT_DEVICEREMOVECOMPLETE
    23:31:17.869 (ports 2): nothing new, skipping HID & Ports enum
    23:31:17.882 (ports 2): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    23:31:17.883 (ports 2): nothing new, skipping HID & Ports enum
    23:31:17.960 (loader): stop ignoring usb:0/1D0000/0/1/5
    23:31:18.045 (ports 2): WM_DEVICECHANGE DBT_DEVICEARRIVAL
    23:31:18.045 (ports 2): nothing new, skipping HID & Ports enum
    23:31:18.212 (loader): handle 2b40
    23:31:18.214 (loader): Device came online, code_size = 100
    23:31:18.215 (loader): Board is: NXP IMXRT1062 ROM
    23:31:18.218 (loader): begin operation
    23:31:18.233 (loader): File "C:\Users\Jeffrey\AppData\Local\Temp\arduino_build _195947\Example2_OutputToProcessing.ino.hex", 33792 bytes
    23:31:18.236 (loader): File "Example2_OutputToProcessing.ino.hex". 33792 bytes
    23:31:18.239 (loader): set background IMG_ONLINE
    23:31:18.250 (loader): nxp_write: success
    23:31:18.254 (loader): nxp_write: success
    23:31:18.257 (loader): HAB open mode, bootcfg=80018
    23:31:18.259 (loader): Opps, NXP ROM in open mode, but we do not yet have code for this case
    23:31:18.261 (loader): start ignoring usb:0/1D0000/0/1/5
    23:31:18.264 (loader): end operation, total time = 0.043 seconds
    23:31:18.270 (loader): redraw timer set, image 79 to show for 3000 ms
    23:31:18.287 (ports 2): WM_DEVICECHANGE DBT_DEVNODES_CHANGED
    23:31:18.287 (ports 2): nothing new, skipping HID & Ports enum
    23:31:21.270 (loader): redraw, image 9





    Please advise,
    Jeff

  2. #2
    Junior Member
    Join Date
    May 2021
    Posts
    17
    Hi,

    Is there an update to this issue? I'd like to load firmware, but cannot. I see the loader error at line
    23:31:18.259

    "(loader): Opps, NXP ROM in open mode, but we do not yet have code for this case " and suspect that is the cause.

    Should I be waiting for a loader update or is my board damaged?

    I am hoping there is something I can do to set the board in a state that the loader then works.

    Please advise,
    Thanks,
    Jeff

  3. #3
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,265
    Not sure if @PaulStoffregen saw this - seems only he would recognize that odd 'open mode' error.

    Has the 15 second Restore been done? That might restore normal function.

    > with T_4.1 powered
    -> Press and hold the Button
    -> watching for a Flash on the USB end RED LED at about 15 seconds
    -> When FLASH is seen release the button and watch

    After the Flash and release the RED LED should light and remain lit for some ~30 seconds in some fashion while the onboard FLASH is formatted and other settings restored.

    When the RED LED goes out the Teensy should be Restored to Factory Blink

    --> Do these steps proceed as indicated?

    Was the T_4.1 purchased from PJRC or a distributor? Saw a post linking to eBay offering half priced T_4.1's

  4. #4
    Junior Member
    Join Date
    May 2021
    Posts
    17
    I tried the 15 second restore but it did not work as expected.

    I did see the short quick flash after about 15 seconds of pressing the button, but the device never showed a stead red light to indicate it was reloading the blink program.

    The factory blink program was never reloaded/installed.

    The device was purchased on May 8th from Amazon.
    Jeff

  5. #5
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    15,265
    Anything soldered or connected to the teensy?

    Does it look like the posted PJRC images of a T_4.1 in exact detail? Any missing parts?

  6. #6
    Junior Member
    Join Date
    May 2021
    Posts
    17
    The headers are soldered to it.
    It worked perfectly the last time I used it a few months ago. It has sat idle.
    It was last used to drive a SmartMatrix board that connected to an RGB panel. That is probably still running.

    There appears to be no missing parts. It appears to have some life in it based on some LEDS flashing.

    It can communicate with the Windows 10 PC. By that I mean, when the loader asks for the button to be pressed, the Windows 10 PC knows when the button is pressed, but then errors out.
    Jeff

  7. #7
    Junior Member
    Join Date
    May 2021
    Posts
    17
    Hello, Does anyone have advice as to how I can revive my Teensey? Is there a way to set it in a state that I can then program it. Thanks,Jeff

  8. #8
    Senior Member
    Join Date
    Feb 2020
    Posts
    104
    Did you resolve? I have a couple of Teensy MicroMods not responding, one did report the Opps message before giving up. completely.

    I did see the Opps message on another one, was able to recover by holding down the boot button during powerup and releasing afterwards.

  9. #9
    Junior Member
    Join Date
    May 2021
    Posts
    17
    Quote Originally Posted by TeensyWolf View Post
    Did you resolve? I have a couple of Teensy MicroMods not responding, one did report the Opps message before giving up. completely.

    I did see the Opps message on another one, was able to recover by holding down the boot button during powerup and releasing afterwards.
    I did not resolve this. My Teensey still has this problem. I'm wondering how much to really invest in Teensey system if this problem tends to happen and there is no way out. I was thinking I could solder some wires and close the NXP memory to get it going?? Then it would be normal.

    Yet, I did buy a new Teensey and that works fine. Hopefully, a fix can revive my dead one.

  10. #10
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    25,215
    @c172jeff - Sorry, I missed this thread earlier.

    First, to answer about "Opps, NXP ROM in open mode, but we do not yet have code for this case", it means your Teensy wasn't able to access the flash memory chip to boot up. Instead it went into a special fallback mode using on the on-chip ROM, because it couldn't access any other memory.

    This result by itself doesn't necessarily mean the hardware has failed. It's possible to get "NXP ROM in open mode" by programming invalid data into the first 512 bytes of the flash memory, which are used at boot time to configure optimized flash access. Normally this shouldn't happen if you only upload from Arduino. But it can happen if you copy a HEX file (without the matching ELF file) meant for a completely different board and use File > Open in Teensy Loader to open it and then program it onto your Teensy. Teensy Loader can only detect if the hardware was really meant for your board if it finds a matching ELF file... which is always present when using Arduino.

    You can also get "Opps, NXP ROM in open mode" if you edit the bootdata.c file and change the contents of the FlexSPI_NOR_Config[] array. Again, not something pretty much anyone does... but the error by itself can mean wrong data got stored in that part of the flash chip.

    But this error while doing the 15 sec restore is a pretty strong indication the flash chip or connectivity between the flash chip and processor has failed.

    I tried the 15 second restore but it did not work as expected.

    I did see the short quick flash after about 15 seconds of pressing the button, but the device never showed a stead red light to indicate it was reloading the blink program.
    Did you buy this Teensy 4.1 direct from PJRC or from a distributor?

  11. #11
    Junior Member
    Join Date
    May 2021
    Posts
    17
    Thanks Paul, I bought the board from Amazon. Are you selling through Amazon?

    Is that a valid distributer? Where should I be buying the boards from?
    I guess my Teensey must be damaged.

  12. #12
    Administrator Robin's Avatar
    Join Date
    Oct 2012
    Location
    PJRC Global Headquarters
    Posts
    325
    Quote Originally Posted by c172jeff View Post
    Thanks Paul, I bought the board from Amazon. Are you selling through Amazon?

    Is that a valid distributer? Where should I be buying the boards from?
    I guess my Teensey must be damaged.

    We do have official distributors who sell through Amazon.

    Would you send me an email with your order details. We would like to arrange to send you a replacement.
    robin at pjrc

    -Robin

  13. #13
    Junior Member
    Join Date
    May 2021
    Posts
    17
    Thank you Robin, That's really nice. I will private message you the order details. I printed a pdf from my Amazon Account of the purchase/address of the my order. It was sold through a seller on Amazon names "3DMakerWorld, Inc."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •