recovery.cfg file seems not flashed and later - roboRIO Imaging Tool - NI System Configuration: This operation is not permitted

[yvonb]

Problem Description

1- Conditions before the tests

  - The latest flashing tools are installed from this link;

        https://www.ni.com/en/landing/first.html

  - I'm using a roboRIO 1.0 (no SD card)
  - Laptop Dell - Windows 11 with the AVG Firewall disabled
  - My computer has only letters and numbers in its name
  - All network interfaces (Ethernet and WiFi) are disabled
  - The connection with the robotRIO is USB (cable Type-A to Type-B)

2- Need flashing from the recovery.cfg file

  When I boot the roboRIO in safe mode (holding the reset button for at least 5 seconds) I get:

  2.1 Power LED is green

  2.2 When I release the reset button it become yellow for 20 secs (but does not blink 3 times)
       The roboRIO does not seems in safe mode state

  2.3 After I get a permanent double flashing status
       This means "Software Error Reimage robotRIO"

  3.- Ok, let's try to reimage the software

  3.1 I download recovery.cfg file.
  3.2 I using a Windows USB FAT32 flash drive,
  3.3 I copy the recovery.cfg file on the flash drive.
  3.4 Then turn off your roboRIO.
  3.5 Insert the FAT32 formatted flash drive (with only the CFG file on it)
        into one of the two USB ports on the roboRIO. I'm using a Type-A to Type-A cable
        for this. The robotRIO is not wired to anything else.
 

  3.6 While holding down the Reset button, turn on the roboRIO.

   The status that I get is as follow;

    3.6.1 No leds for 2-3 seconds
    3.6.2 The Power LED turn green
    3.6.3 The Status LED turn yellow (no blink)
    3.6.4 After 5 secs I see some USB blinking key activity for another 5 sec
           (I'm using a using a USB key with a status LED on it).
    3.6.5 Then the data transfert is stopped on the USB key (black no blinking)
    3.6.6 After another 30 secs the USB key blink quickly for 2 sec then stops,
            and the status LED is turned off (look like a Linux unmount).
    3.6.7 During all this time the status LED always stays yellow, no blink for 40-50 sec.
    3.6.8 When the status LED turn off after 2-3 sec it start the 2 blink sequence.

           At this point I should assume that the roboRIO is ready to be completely
           reflashed but.

    However (25% of the time)

          Sometimes the USB recovery flashing fail just after 3.6.5 and the status LED
          start immediately blinking.

4- Running the roboRIO Imaging Tool as administrator.

    After executing the previous steps I get the following results with the the Imaging Tool.

    The program does not discover anything as showed in the left bottom side of the Window.
    The format target option is disabled and if I try to update the firmware I get the following the message;

    NI System Configuration: This operation is not permitted for the target and the resource.

Need some help now...

[mshafer]

Hello yvonb, thank you for posting on the forums. I'm Matthew with NI.

On step 2 / 2.3 -> to clarify, you're holding the reset button down while the roborio is given power and you observe this light pattern?

3.6.8 -> when the imaging is done, all LEDs (including power) should turn off for a moment while the roborio reboots itself.

If it is returning to a 2-blink pattern immediately, that indicates to me that it failed to apply the image.

Can you try with the usb drive inserted directly (without the A to A cable)?

Can you try a different usb drive?

(For reference, step 8 here has a couple of things to try if imaging is not successful)

[yvonb]

You will find in the following videos what's  I'm doing;

-  The first video '2.1-2.3 Power on Reset' follow the sequence

    described previously.

-  The next two videos "3.4-3.6.5 USB Flash" is the sequence also

    described previously. However after 3.6.6 - 3.6.8 I do not get the same

    sequence as described !!!

    After the cfg seems copied we get the double blink state after

    20 secs (no 50secs). I also tested with another USB key (third video)

    with the same result..    

Finally I'm not using any USB A to A cable.
    I have during the previous days the permanent status blink a couple
    of time. This board is getting an erratic behaviour.

[yvonb]

Last thing I can do to document the issue.

Same sequence then the previous post.

A USB key was put on a hub repeater. The repeater on one side
attached to the roboRIO. On the other side the repeater was attached

to Windows in USB mode. I got the Wireshark tracefile included

in this post. Cannot guaranty if this was some traffic between Window

and the USB key and-or we get some data transfer from the roboRIO. 

Can help or not.

note: rename test1.cap -> test1.pcap to open the file with Wireshark.

[mshafer]

I sent you a direct message with next steps.