Skip to content
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

Support the STM NUCLEO_L433RC-P board #5591

Merged
merged 10 commits into from
Dec 12, 2017

Conversation

helmut64
Copy link
Contributor

I added support for a new the target NUCLEO_L433RC-P board.
This branch NUCLEO_STM32L433_NEW supersedes the NUCLEO_STM32L433_SUPPORT branch (#5230) where I had merging problems.
It basically contains all my 433 changes based on the latest master branch.
I have carefully verified (via diff) every single file I changed. It compiles fine for the 433 and 432 targets.
Sorry for any inconvenience.
Regards Helmut
@0xc0170 @bcostm

@theotherjimmy theotherjimmy changed the title New support for the STM NUCLEO_L433RC-P board (New branch) Support the STM NUCLEO_L433RC-P board Nov 27, 2017
@bcostm
Copy link
Contributor

bcostm commented Nov 28, 2017

We have run the mbedOS 5 and 2 tests again on this branch on the NUCLEO_L433RC_P and they are all PASS. We verified also the NUCLEO_L432KC and it is ok too.
Thanks again.

report_OS5_NUCLEO_L433RC_P.zip
report_OS2_NUCLEO_L433RC_P.zip

@0xc0170 0xc0170 self-requested a review November 30, 2017 17:32
@helmut64
Copy link
Contributor Author

helmut64 commented Dec 3, 2017

@0xc0170 Martin, this is ready to merge that I don't run into the rebase request again.

@0xc0170
Copy link
Contributor

0xc0170 commented Dec 4, 2017

@0xc0170 Martin, this is ready to merge that I don't run into the rebase request again.

Reviewing now, as soon as done, we run CI

@0xc0170
Copy link
Contributor

0xc0170 commented Dec 4, 2017

/morph build

@mbed-ci
Copy link

mbed-ci commented Dec 4, 2017

Build : SUCCESS

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

Triggering tests

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

@mbed-ci
Copy link

mbed-ci commented Dec 4, 2017

@mbed-ci
Copy link

mbed-ci commented Dec 4, 2017

@helmut64
Copy link
Contributor Author

helmut64 commented Dec 13, 2017

@bcostm now after it is merged and ready, I believe you can add (or prepare) the board to supported mbed hardware boards page. I don't know if something else needs to be done that it shows up as a new target in the online compiler.

I am glad that it is merged and will be ready with the next mbed version

Thanks to everyone.

PS: My new MyHome LoRa Board with the STM32L433 and the STM LSM303AGR cannot wait to see the new 433 support. The solution should work 5-10 years on two AAA batteries as a door sensor. I will assemble the new PCB it tomorrow. More details will be available here: http://www.radioshuttle.de

myhome lora board

@bcostm
Copy link
Contributor

bcostm commented Dec 13, 2017

Hi Helmut

I believe you can add (or prepare) the board to supported mbed hardware boards page
Yes it's in my plan. I'll do it this week.

I don't know if something else needs to be done that it shows up as a new target in the online compiler.
It's ARM to decide when to make it available on the online compiler. Usually it is done after they have received boards and made tests on it. It will take a couple of weeks before it is available. I'll keep you informed.

PS: Your board board looks great. I will check details when they'll be available.

@helmut64
Copy link
Contributor Author

@bcostm are you sending ARM some Nucleo 433RC-P boards? (I can also do so if this helps.).
PS: Thanks for the feedback regarding the board, the most important point is the RadioShuttle protocol which uses peer to peer networking and is way better than the LoRaWAN protocol.

@bcostm
Copy link
Contributor

bcostm commented Dec 13, 2017

are you sending ARM some Nucleo 433RC-P boards? (I can also do so if this helps.).
Yes. Thanks for proposing but it's ok, I manage it.

@helmut64
Copy link
Contributor Author

myhome lora

The board works completely with the new Nucleo STM32L433 target.
@0xc0170 the only missing part is to activate the new Nucleo Board in the Online compiler.

@helmut64
Copy link
Contributor Author

helmut64 commented Jan 5, 2018

@bcostm a happy new year, I have an offtopic question.
The L4 has 1k OTP memory which I successfully programmed using USB-DFU boot. Do you have any idea where I can find the registers and description for the OTP feature. It is not available in the L4 data sheets nor in the L4 reference manuals. Or is the L4 DFU source somewhere available that I can check this? Thank you, Helmut.

@bcostm
Copy link
Contributor

bcostm commented Jan 5, 2018

Hi Helmut,
Thanks and happy new year too.

registers and description for the OTP feature ?
I don't understand what do you need that is it not written in DS or RM ? If you look for something that it is not written in these documents that would mean that these information are not public...

Can you ask also on STM32 forum (https://community.st.com/community/stm32-community/stm32-forum) ?

@bcostm
Copy link
Contributor

bcostm commented Mar 15, 2018

the only missing part is to activate the new Nucleo Board in the Online compiler.

This board is live on mbed since yesterday I think.

@helmut64
Copy link
Contributor Author

Very good, thank you.
PS: In the PinNames.c the LED is defined with PA5 but should be PB13, can you do the change for should I prepare a patch.

@helmut64 helmut64 deleted the NUCLEO_STM32L433_NEW branch March 15, 2018 13:16
@bcostm
Copy link
Contributor

bcostm commented Mar 15, 2018

I have already done the fix in PR 6330

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