X20CP0482 Boot Mode Issue

Ask Questions Controls & Vision
1

Screenshot 2026-06-11 142734
Screenshot 2026-06-11 1427341028×553 42 KB

Hello B&R community,

I’m trying to perform an Operating System Transfer to an X20CP0482 CPU while it’s in BOOT mode, but I’m running into several issues I can’t fully explain. Hoping someone can help me understand the root cause.

Environment

Hardware: X20CP0482 (X20 Compact-S CPU)

AR Version (selected during OS Transfer): S4.93

Automation Studio: 4.12

Connection: Ethernet, INA Port 11159, IP 192.168.10.100

Project: Existing application with multiple modules (OPC UA, mapp, HMI, etc.) — not an empty project

OS Transfer option used: “Modules from project scheme”

Issue 1 — “Operation Failed!” during OS Transfer in BOOT mode

When the CPU is in BOOT mode and I attempt to transfer the Operating System, the transfer fails with an “Operation Failed!” dialog.

The build itself shows 0 errors / 0 warnings, so the project compiles cleanly.

Issue 2 — Power cycle sometimes works (intermittent)

After power-cycling the hardware (OFF for ~10 seconds, then ON), the OS Transfer in BOOT mode sometimes succeeds — but not consistently.

The behavior seems unpredictable: it works once, then fails again on the next attempt without any code or configuration change.

Issue 3 — “Waiting for reconnection…” after OS Transfer

After an OS Transfer attempt, Automation Studio shows “Waiting for reconnection…” indefinitely.

I’ve read on the forum that this happens because the IP address is not being applied to the CPU after the transfer.

If I cancel that dialog, the CPU stays in BOOT mode with IP 0.0.0.0.

Then, if I run “Set IP Parameters” again from BOOT mode, the CPU transitions to RUN mode successfully — but the mechanism is unclear to me.

What I’ve tested

  • Clean Configuration from BOOT mode
  • Running Automation Studio as Administrator
  • Power-cycling the hardware multiple times
  • Re-applying “Set IP Parameters” from BOOT mode after Cancel (this is the only reliable workaround so far)
  • Verified Ethernet connectivity and IP/subnet:
    • IP: 192.168.10.100
    • Subnet: 255.255.255.0
    • INA node: 2
    • Port: 11159

Questions

1. What is the root cause of “Operation Failed” during OS Transfer when the CPU is in BOOT mode?

2. Why does a power cycle sometimes allow the OS Transfer to succeed, but not consistently?

3. Why does “Waiting for reconnection…” appear?

Is the new IP not being applied to the CPU during/after OS Transfer, or is something else blocking the reconnection?

4. After Cancel and “Set IP Parameters” from BOOT mode, why does the CPU successfully transition to RUN mode?

What’s the underlying sequence?

BOOT → IP assignment → AR start → RUN

5. Is there a recommended procedure to reliably transfer the OS to an X20CP0482 in BOOT mode with AS 4.12?

Or is the proper recovery path to re-write the CompactFlash card using “Create Compact Flash”?

Any insight into the BOOT mode → OS Transfer → IP assignment → reconnection sequence would be very helpful.

Thank you!

2

Hi @Gyun ,

I can only answer to few questions (busy day…), but I remember we already answer to similar questions in other posts

AR Version (selected during OS Transfer): S4.93
Automation Studio: 4.12

That’s good you already installed the latest AR available for X20CP042 and AS 4.12

Or is the proper recovery path to re-write the CompactFlash card using “Create Compact Flash”?

There is no CompcactFlash on X20CP042

image
image271×438 64.3 KB

Which AS are you using? 4.12.2/3/4/5/6/7/8/9…
Latest available:

image
image298×207 1.96 KB

Which PVI version have you installed?
Latest for AS 4.12:

image
image1456×413 28.8 KB

Thanks
Ciao
Valerio

3

Hello, thank you for replying to me while you are busy.

I useing Automation Studio 4.12.8.41

PVI has never been installed separately
Attached is a picture of PVI Manager information that comes out when I run AS4.12 on my laptop.

I don’t know why the operating fail is happening
Waiting for reconnection in boot mode is
I checked that the X20CP0482 didn’t get the IP information right, so I kept waiting for the reconnection. If I cancel waiting for Reconnection, the hardware IP will be searched for 0.0.0.0 in the Online Hardware Navigation window.
If you put the IP information back in here and try to connect, the hardware will only receive the IP information and go into a RUN state. The above two phenomena continue to occur in BOOT mode, and I was wondering if there was a cause or a solution, so I left this article.

image
image1421×755 71.9 KB

4

Hi @Gyun ,

Issue 1/2
When the CPU is in BOOT mode and I attempt to transfer the Operating System, the transfer fails with an “Operation Failed!” dialog.
After power-cycling the hardware (OFF for ~10 seconds, then ON), the OS Transfer in BOOT mode sometimes succeeds — but not consistently.

I’m with you, when the system in BOOT mode you should transfer the OS all the time with no issue:

image
image1458×339 151 KB

so you have found a bug, in this situation we have to follow a guideline we have in our Community: If you found a bug in an official B&R software, please report this directly to your local B&R Support team. The B&R Community is not the official channel for bug reporting. The exception is for bugs related open-source developments within the community itself. The same restriction applies for quality topics.

Issue 3 — “Waiting for reconnection…” after OS Transfer

After an OS Transfer attempt, Automation Studio shows “Waiting for reconnection…” indefinitely.

I’ve read on the forum that this happens because the IP address is not being applied to the CPU after the transfer.

If I cancel that dialog, the CPU stays in BOOT mode with IP 0.0.0.0.

The IP address in Boot mode will default to 0.0.0.0 unless you set it with SNMP. However, it will revert after a restart back to 0.0.0.0. To keep it at the IP you’ve set in the project, you’ll need to get the controller to stay in RUN mode.

5

Hello @valerio.manenti

Looking for a community post, I found the cause and was able to answer the person who asked me.
Thank you for your time.