Skip to content

Conversation

rajkan01
Copy link
Contributor

@rajkan01 rajkan01 commented Sep 16, 2021

Summary of changes

  • ROM size is required in callback_big and compliance printf greeentea test for finding out the number of test cases to be enabled to avoid flash overflow, but when we copy the "mbed-rom-size" config from index.json to targets.json causes the build failure for LPC1114 as MBED CLI1 expects that if any of the mem (ROM, RAM) configs are present in targets.json should have bootloader support, hence introducing new rom-size using "config" in LPC1114 in targets.json to generate MBED_CONF_TARGET_ROM_SIZE by Mbed CLI1 and Mbed CLI2 macro which can be used in the greentea test.
  • Add new rom-size config to the 15 targets which already have mbed_rom_size config in "targets.json"
  • Replace MBED_ROM_SIZE with MBED_CONF_TARGET_ROM_SIZE
  • The "minimal_printf" greentea test has test cases for the different data types (%d, %u, %x, %ld, %lu, %lx %llx) that require a minimum above 36kb ROM to build all test cases. LPC1114 target has only 32KB ROM memory, so these changes excluding 3 test cases of data types %lld, %llu, %llx to bring down to meet target minimum ROM size

Impact of changes

With these changes, minimal_printf greentea test can avoid overflow ROM issue

Migration actions required

None.

Documentation

None.


Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers


@rajkan01 rajkan01 force-pushed the fix_lp1114_flash_overflow_issue branch from 5535931 to a391837 Compare September 16, 2021 13:18
@rajkan01 rajkan01 force-pushed the fix_lp1114_flash_overflow_issue branch from a391837 to 43784bc Compare September 16, 2021 14:05
- ROM size is required in callback_big and compliance printf greeentea test
for finding out the number of test cases to be enabled to avoid flash
overflow, but when we copy the "mbed-rom-size" config from index.json
to targets.json causes the build failure for LPC1114 as MBED CLI1 expects
that if any of the mem (ROM, RAM) configs are present in targets.json
should have bootloader support, hence introducing new rom-size using
"config" in LPC1114 in targets.json to generate MBED_CONF_TARGET_ROM_SIZE
by Mbed CLI1 and Mbed CLI2 macro which can be used in the greentea test.

- Add new rom-size config to the 15 targets which already have mbed_rom_size
config in "targets.json"
…nary size

The "minimal_printf" greentea test has test cases for the different data types
(%d, %u, %x, %ld, %lu, %lx %llx)  that require a minimum above 36kb ROM
to build all test cases. LPC1114 target has only 32KB ROM memory,
so these changes excluding 3 test cases of data types %lld, %llu, %llx
to bring down to meet target minimum ROM size
@rajkan01 rajkan01 force-pushed the fix_lp1114_flash_overflow_issue branch from 43784bc to b712589 Compare September 16, 2021 14:10
#define LLONG_MIN INT64_MIN
#endif

#define TEST_MIN_REQ_ROM_SIZE (36 * 1024)
Copy link
Contributor

Choose a reason for hiding this comment

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

Is 36 KiB enough to run the tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes probably enough

Copy link
Contributor

Choose a reason for hiding this comment

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

How do we know?

@rajkan01 rajkan01 requested a review from Patater September 17, 2021 14:38
@ciarmcom ciarmcom added the stale Stale Pull Request label Sep 22, 2021
@ciarmcom
Copy link
Member

This pull request has automatically been marked as stale because it has had no recent activity. @rwalton-arm, @Patater, please complete review of the changes to move the PR forward. Thank you for your contributions.

@ciarmcom ciarmcom removed the stale Stale Pull Request label Sep 24, 2021
@0xc0170 0xc0170 added the release-type: patch Indentifies a PR as containing just a patch label Sep 28, 2021
@mergify
Copy link

mergify bot commented Oct 7, 2021

This PR cannot be merged due to conflicts. Please rebase to resolve them.

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 9, 2022

We are closing this pull request due to inactivity

@0xc0170 0xc0170 closed this Feb 9, 2022
@mergify mergify bot removed needs: work release-type: patch Indentifies a PR as containing just a patch labels Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants