Looking for explanation of P1633 on 360

I have a 360 that is cranking but not starting. When the Check OK message comes on, I can connect to either ECU via a Launch scanner and the single error code is P1633: configuration error (Bank 2).

I would like to find an explanation of that code and what to look for. Anyone?

 

I have that, I just can't tell what is wrong yet.

 

Battery is not the problem.

 

OK, let me provide some context.

This factory 6-speed 360 has been having an intermittent starting issue for a while and recently it is permanently inoperative -- crank but no starting at all. The sequence of events is:

Last week:
1. Get in, disable immobilizer, insert the key and turn it to on.
2. Either a green Check OK message will come on the instrument panel, or an orange ASR comes on.
3. Turn key to Start, engine cranks and cranks but no ignition
4. Plug in a Launch scanner.
4a. IF the Check OK was on, then the scanner can see both ECUs left and right. Selecting Bank 1 (Master ECU) and read two error codes passed over from Bank 2 ECU. Selecting Bank 2 (Slave ECU), and read the same two error codes: P1633, P1199.
4b. If ARS message is on, the scanner cannot see either of the ECUs. A generic OBD2 scanner has the same issue so it's not the scanner.

This week, believing that the two ECUs are having problem with the Immobilizer, I deleted the immo function. And now the sequence is:
1. Get in, insert the key and turn it to on.
2. Either a green Check OK message will come on the instrument panel, or an orange ASR comes on.
3. Turn key to Start, engine cranks and cranks but no ignition
4. Plug in a Launch scanner.
4a. IF the Check OK was on, then the scanner can see both ECUs left and right. Selecting Bank 1 (Master ECU) and read one error code passed over from Bank 2 ECU. Selecting Bank 2 (Slave ECU), and read the same one error codes: P1633. So deleting the Immo made progress by reducing to a single P1633 code.
4b. If ARS message is on, the scanner cannot see either of the ECUs. A generic OBD2 scanner has the same issue so it's not the scanner.

So according to Trev360, after key turning on, if the two ECUs cannot communicate to each other, the Orange ASR message flashes on the instrument scanner.

The pattern is: No start, code P1633, ASR message and inability to connect to the OBD port (via K L lines).

It was suggested that perhaps both ECUs are acting as both rights or both lefts ECUs via pin 60. That would prevent ECUs from exiting self-test and the OBD2 port is not enabled.
This morning, pin 60 of the bank 2 (slave ECU) was checked and there is a solid Ground signal. The back of the connector was opened to find no frayed wires. Probing between pin 60 and every other pin shows no short circuit in the harness to pin 60. Pin 60 of the master ECU was left with no wire at all so the pin would float to high logic. It does not look like a set up issue.

So the problem defines itself as: Code p1633, no communication among the two ECUs, no OBD port.

I have checked the second CAN port dedicated to exclusive communication between the two ECUs and lines continuity exists, as well as a termination resistor of 120 ohms. I should/will put a digital oscilloscope on the two CAN lines to check the integrity of the signals while powering up.

As of today, no start. If someone can explain the relationship between the code 1633, the ASR message, and the non-op OBD2 port, perhaps we can solve this mess of a car.