Skip to content

Flash support: Add flash support for LPC54114 & LPC546XX #6198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 15, 2018

Conversation

mmahadevan108
Copy link
Contributor

@mmahadevan108 mmahadevan108 commented Feb 23, 2018

Passed the flash tests

  1. LPC54114:
    mbedgt: test on hardware with target id: 105400001b4ee77600000000000000000000000097969905
    mbedgt: test suite 'mbed-os-tests-mbed_hal-flash' .................................................... OK in 14.28 sec
    test case: 'Flash - buffer alignment test' ................................................... OK in 0.14 sec
    test case: 'Flash - clock and cache test' .................................................... OK in 0.10 sec
    test case: 'Flash - erase sector' ............................................................ OK in 0.14 sec
    test case: 'Flash - init' .................................................................... OK in 0.08 sec
    test case: 'Flash - mapping alignment' ....................................................... OK in 0.05 sec
    test case: 'Flash - program page' ............................................................ OK in 0.24 sec
    mbedgt: test case summary: 6 passes, 0 failures

  2. LPC564XX:
    mbedgt: test on hardware with target id: 105600001984a78e00000000000000000000000097969905
    mbedgt: test suite 'mbed-os-tests-mbed_hal-flash' .................................................... OK in 14.01 sec
    test case: 'Flash - buffer alignment test' ................................................... OK in 0.14 sec
    test case: 'Flash - clock and cache test' .................................................... OK in 0.06 sec
    test case: 'Flash - erase sector' ............................................................ OK in 0.13 sec
    test case: 'Flash - init' .................................................................... OK in 0.04 sec
    test case: 'Flash - mapping alignment' ....................................................... OK in 0.05 sec
    test case: 'Flash - program page' ............................................................ OK in 0.23 sec
    mbedgt: test case summary: 6 passes, 0 failures

@mmahadevan108
Copy link
Contributor Author

cc @0xc0170 @maclobdell

int32_t ret = -1;
uint8_t buf[FSL_FEATURE_SYSCON_FLASH_PAGE_SIZE_BYTES];

if (address == 0) { // Check for Vector Table
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does this work with bootloader, or does not have any affect? (not sure what n represents)

From the code, n gets overwritten on line 81 (is it just reusing the variable? wouldn't it be more clear to have two separate ? n on the line 81 represents sector number, here on this line it is signature calculation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is required by the ROM bootflow.


0x1C Vector checksum (set by tool vendors).


You are right, the variable is reused for a different purpose. If it is not clear we can create a different variable.

Copy link
Contributor

@0xc0170 0xc0170 Mar 7, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, the variable is reused for a different purpose. If it is not clear we can create a different variable.

Please do, should help clarify the intention of those 2 variables in this function.

The rest LGTM

@mmahadevan108
Copy link
Contributor Author

@0xc0170 . Anything else needed for this PR.

1 similar comment
@mmahadevan108
Copy link
Contributor Author

@0xc0170 . Anything else needed for this PR.

@mmahadevan108 mmahadevan108 force-pushed the Add_LPC54XXX_Flash_Support branch from d9f9b4e to 3f30296 Compare March 7, 2018 19:08
@mmahadevan108
Copy link
Contributor Author

@0xc0170 PR has been rebased and updated per review comments

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 8, 2018

/morph build

@mbed-ci
Copy link

mbed-ci commented Mar 8, 2018

Build : SUCCESS

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

Triggering tests

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

@mbed-ci
Copy link

mbed-ci commented Mar 8, 2018

@mbed-ci
Copy link

mbed-ci commented Mar 8, 2018

@mmahadevan108
Copy link
Contributor Author

mmahadevan108 commented Mar 8, 2018

@0xc0170 I don't think the TEST FAILURE is due to this PR.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 9, 2018

/morph test

@mbed-ci
Copy link

mbed-ci commented Mar 9, 2018

@cmonr cmonr merged commit 95fb33f into ARMmbed:master Mar 15, 2018
@mmahadevan108 mmahadevan108 deleted the Add_LPC54XXX_Flash_Support branch March 19, 2018 14:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants