AM263P4: AM263P4 OSPI boot pinmux – SysConfig default does not match ROM boot requirements (SPRABJ8D), leads to unbootable HW

Hello TI,

we found a serious inconsistency between:

1. What ROM Boot (SPRABJ8D) expects for OSPI pinmux
   and

2. What SysConfig proposes as the default OSPI pinmux

The result is hardware that cannot boot from OSPI, although SysConfig makes it look like it should.

Here is what happened:

1) SPRABJ8D Table 6-5

SPRABJ8D Table 6-5 lists OSPI pins used by ROM boot.

However:

• It uses labels like GPIO0, GPIO1, etc.

• It is never stated what these GPIO numbers correspond to physically.

• They cannot be mapped to pads/balls from that document alone.

So Table 6-5 cannot be directly used for PCB routing.

2) SysConfig default OSPI pinmux

SysConfig offers an OSPI configuration that does not match the ROM boot requirements.

There is no warning that these pins cannot be used for ROM boot. (Nothing in documentation, nothin in SysCofig which create incompatible config AS DEFAULT OPTION (image is taken from fresh SysConfig project where is ONLY flash with automatic OSPI configuration)

3) Real effect on our hardware

We followed SysConfig output when routing OSPI flash.

Result:

• OSPI works after boot (runtime pinmux)

• OSPI boot does not work (ROM cannot see flash)

We now have 10 prototype boards that cannot boot.

4) ControlCard routing

We looked at the AM263px ControlCard/LaunchPad schematic.

It uses OSPI pins different from SysConfig defaults, and those match SPRABJ8D.

5) What we need clarified

Please confirm:

• ROM boot uses only one OSPI pinmux configuration.

• SysConfig alternatives are runtime only, not ROM-compatible.

• Table 6-5 GPIO labels need explicit mapping to pads/balls.

And please consider:

• Adding a SysConfig warning when selecting OSPI pins that cannot work for ROM boot.

This would have prevented our mistake.

Thanks,
Jiri Dobry