Skip to content

add support for STM32L443RC & WISE-1510 #5904

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
Jan 30, 2018
Merged

add support for STM32L443RC & WISE-1510 #5904

merged 1 commit into from
Jan 30, 2018

Conversation

ithinuel
Copy link
Member

@ithinuel ithinuel commented Jan 23, 2018

Description

This PR add support for the STM32L443RC and the WISE-1510 module.
This was tested with @kivaisan on mbed-os-example-lora

Status

MERGED

Todos

  • Tests
  • Documentation

@ithinuel ithinuel changed the title add basic support for STM32L443RC & WISE-1510 add support for STM32L443RC & WISE-1510 Jan 23, 2018
@@ -1472,6 +1472,23 @@
"release_versions": ["2", "5"],
"device_name": "STM32L433RC",
"bootloader_supported": true
},
"WISE_1510": {
Copy link
Contributor

Choose a reason for hiding this comment

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

no release version? will be added later?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure about which revision it's aiming.
Should it be current 5.7 or next release 5.8 ?

Copy link
Contributor

Choose a reason for hiding this comment

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

release_versions can be 2 or 5 or both. I assume 5 should be defined here

Copy link
Member Author

Choose a reason for hiding this comment

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

oh, ok, I add it now.

Copy link
Collaborator

@jeromecoutant jeromecoutant left a comment

Choose a reason for hiding this comment

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

Hi
Here is a quick review
Thx

.gitignore Outdated
@@ -72,6 +72,9 @@ debug.log
# Cscope
cscope.*

# Ctags
tags
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not related to the PR

Copy link
Contributor

Choose a reason for hiding this comment

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

Should be sent via separate PR

.ANY (+RO)
}

RW_IRAM1 0x20000000 0x0000C000 { ; RW data 48k L4-SRAM1
Copy link
Collaborator

Choose a reason for hiding this comment

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

In STM32L443, SRAM2 and SRAM1 and continuous.
You can prefer to get a bigger SRAM1. See #5171

Copy link
Member Author

@ithinuel ithinuel Jan 24, 2018

Choose a reason for hiding this comment

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

These two ranges offer different features namely the hardware parity check and the standby retain mode on SRAM2.
In order to let the end-user free to choose to use it or not, shouldn't we rather add a special section to allow this use case and avoid the user to tweak the linker script him/herself ?

{
FLASH (rx) : ORIGIN = MBED_APP_START, LENGTH = MBED_APP_SIZE
SRAM2 (rwx) : ORIGIN = 0x1000018C, LENGTH = 16k - 0x18C
SRAM1 (rwx) : ORIGIN = 0x20000000, LENGTH = 48k
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same comment, you can increase RAM size from 48k to 64k

}
},
"release_versions": ["5"],
"device_has_add": ["ANALOGOUT", "LOWPOWERTIMER", "SERIAL_FC", "SERIAL_ASYNCH", "CAN", "TRNG", "FLASH", "AES"],
Copy link
Collaborator

Choose a reason for hiding this comment

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

DEVICE_AES doesn't exist ?

Copy link
Member Author

Choose a reason for hiding this comment

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

Should it be the macro MBEDTLS_CONFIG_HW_SUPPORT instead ?

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 24, 2018

Please check travis failures

@ithinuel
Copy link
Member Author

/morph build

@mbed-ci
Copy link

mbed-ci commented Jan 26, 2018

Build : SUCCESS

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

Triggering tests

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

@mbed-ci
Copy link

mbed-ci commented Jan 26, 2018

@cmonr
Copy link
Contributor

cmonr commented Jan 29, 2018

/morph build

@cmonr
Copy link
Contributor

cmonr commented Jan 29, 2018

@jeromecoutant Are you good with the latest commits for this PR?

Copy link
Collaborator

@jeromecoutant jeromecoutant left a comment

Choose a reason for hiding this comment

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

Increase RAM size from 48k to 64k is optional, and can be checked later.

@mbed-ci
Copy link

mbed-ci commented Jan 29, 2018

Build : SUCCESS

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

Triggering tests

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

@mbed-ci
Copy link

mbed-ci commented Jan 29, 2018

@mbed-ci
Copy link

mbed-ci commented Jan 30, 2018

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 30, 2018

/morph uvisor-test

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 30, 2018

/morph uvisor-test

@ithinuel
Copy link
Member Author

All green 🕺 !

@ithinuel ithinuel deleted the add-wise-1510 branch January 30, 2018 21:10
@mbed-ci
Copy link

mbed-ci commented Jan 30, 2018

@cmonr
Copy link
Contributor

cmonr commented Jan 30, 2018

@ithinuel Not sure why the above exporter build just ran. If we need some sort of action from you, we'll let you know.

@ithinuel
Copy link
Member Author

ithinuel commented Jan 30, 2018

Ok, no problem, you know where I stand 😉

@cmonr
Copy link
Contributor

cmonr commented Jan 30, 2018

@ithinuel It looks like this PR + #5947 + some unfortunate timing is causing the new build issues.

I'm going to move forward with the revert PR, and once it passes all of its tests, merge it in. After it's merged in, I'd like you to restore your branch, and create a new PR.

The issue appears to have been the timing that the morph build commands occurred between the two PRs.

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.

5 participants