Revert "NUCLEO_F767ZI: Add bootloader support"

[cmonr]

Reverts commit 4d0535a.

Pull request introduced CI bug that causes a serial sync error once greentea tests are started.

Description

After investigation, it was found that the NUCLEO_F767ZI will not sync with greentea, causing our CI tests to slow down and continuously fail. Reverting prior to when bootloader support was added, and reflashing the device appears to solve the problem.

If this is not the only commit causing the issue, other commits will be reverted in this PR.

Status

READY

Migrations

For the time being, this will disable bootloader support for NUCLEO_F767ZI.

Steps to test or reproduce

To reproduce the issue:

• Download mbed-os at 98611c8
• Compile, flash, and test on NUCLEO_F746ZG.
• Power cycle the device.
• Run test again. Sync will fail.

To recover the device:

• Checkout mbed-os prior to STM32F7: Add bootloader support #5821
• Compile, flash, and test on NUCLEO_F746ZG.
• Power cycle the device.
• Run test again. Issue goes away.

[cmonr]

/morph test

[cmonr]

@studavekar @0xc0170 @theotherjimmy @adbridge Feel free to check this over.

Immediately jumping to testing this PR.

[cmonr]

@bcostm, keeping you in the loop.

[mbed-ci]

Test : FAILURE

Build number : 771
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5927/771

[cmonr]

I promise that previous morph command was suppose to be build...

/morph build

[theotherjimmy]

I don't think this is the PR you are looking for. "bootloader support" just allows you to change the start and size of the application.

[mbed-ci]

Build : SUCCESS

Build number : 942
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5927/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

[studavekar]

Looks like root cause cache setting may be :: https://github.com/ARMmbed/mbed-os/pull/5821/files#diff-862e5175fcbe6ee18fd2f54787555ec7R38

[mbed-ci]

Exporter Build : SUCCESS

Build number : 630
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/5927/

[mbed-ci]

Test : FAILURE

Build number : 772
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5927/772

[0xc0170]

/morph test

[0xc0170]

/morph uvisor-test

[bcostm]

I don't think this is the PR you are looking for. "bootloader support" just allows you to change the start and size of the application.

I have also changed the Cache initialization otherwise the application programmed by the bootloader was not running. But the ci-test was pass finally in PR #5821.

[0xc0170]

In the above descriptions by @cmonr , you need to run the test 2x to get the failure from my understanding.

[mbed-ci]

Test : FAILURE

Build number : 773
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/5927/773

[0xc0170]

Looking at the changes this does not revert the cache settings (entire patch), sending a new one