-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
STM32 support is missing #3
Comments
As an example of our Opensource project using STM32F405RGT6 and similar, please refer to: |
Hi @michaesc thx for suggesting new hw support. STM32 is good target too I have considered it, but I lack a device with connectivity, I think the IoT devboard could be a good candidate. Then I know that STM32F4 was or is still supported by iotjs using Nuttx OS: Meanwhile, I only have a STM32F3 (without connectivity) but IIRC it also supports NuttX, that could worth a try. |
FYI, I can share some experiments for STM32F4 using nuttx it's booting shell is appearing fine but not when linked to iotjs... more investigation will be needed, ping me if any interest, I will clean up this draft helper project: https://github.com/rzr/rzr-wip/tree/sandbox/rzr/nuttx/devel/master cc: @Jorgininho |
Hints, Feedback and status update welcome at: |
Hi, FYI, I have basic iotjs support. but http is not working properly yet so more investigation will be needed. Maybe it could be simpler to bring support to this project first: |
Updates here, FYI I just managed to get webthing-iotjs working on "Nucleo-f767ZI" Until it's fully unstreamed I can explain how to use it, just ask me to explain more on this page: Then I'll have to add PWM support, to be tracked at: And in longer term this could be ported to TizenRT too, if anybody want to join doing this ? |
Hi @rzr |
Nothing special, just wanted to let you know as you already merged my patches ;) For your info webthings (http rest devices) can be implemented using arduino API (using stm32duino) or with plain javascript using IoT.js which is based on JerryScript (also used by mbed + @jzorjnz modules) Relate-to: stm32duino/STM32Ethernet#17 Stay tuned, https://social.samsunginter.net/@rzr/100882359240971661#web-of-things-agriculture-20180712rzr# |
@rzr |
Relate-to: jerryscript-project/jerryscript#2838 |
Change-Id: Ia7c8aac06896fad5f004f52ec44bf7cc8bd8d7d0 Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently only one function is defined in it: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently only one function is defined in it: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently only one function is defined in it: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently only one function is defined in that platform header: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently that platform header defines only one function: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently that platform header defines only one function: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 Forwarded: jerryscript-project#1867 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
So far, Only console, http module has been tested. Config file is generated using defconfig, and contains those mandatory options: ``` CONFIG_NET_LOCAL=y CONFIG_NET_TCPBACKLOG=y CONFIG_PTHREAD_MUTEX_TYPES=y CONFIG_RR_INTERVAL=100 CONFIG_SCHED_LPWORKPRIORITY=176 ``` Build flags are relying on mcpu flags. More IO modules to be supported next. Relate-to: rzr/webthing-iotjs#3 Change-Id: Ib44227e33c6b7d07f11687385d788017350e3827 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Currently that platform header defines only one function: "iotjs_stm32f4dis_pin_initialize". It's platform specific and called elsewhere: ./src/modules/iotjs_module_stm32f4dis.c So it's safe to remove this probable leftover to support more boards (STMF7 ones to come). Change-Id: If22dbf1797fec20161203661b044845f55d2e378 Relate-to: rzr/webthing-iotjs#3 Forwarded: #1867 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
So far, Only console, http module has been tested. Config file is generated using defconfig, and contains those mandatory options: ``` CONFIG_NET_LOCAL=y CONFIG_NET_TCPBACKLOG=y CONFIG_PTHREAD_MUTEX_TYPES=y CONFIG_RR_INTERVAL=100 CONFIG_SCHED_LPWORKPRIORITY=176 ``` Build flags are relying on mcpu flags. More IO modules to be supported next. Relate-to: rzr/webthing-iotjs#3 Change-Id: Ib44227e33c6b7d07f11687385d788017350e3827 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
So far, Only console, http module has been tested. Config file is generated using defconfig, and contains those mandatory options: ``` CONFIG_NET_LOCAL=y CONFIG_NET_TCPBACKLOG=y CONFIG_PTHREAD_MUTEX_TYPES=y CONFIG_RR_INTERVAL=100 CONFIG_SCHED_LPWORKPRIORITY=176 ``` Build flags are relying on mcpu flags. More IO modules to be supported next. Relate-to: rzr/webthing-iotjs#3 Change-Id: Ib44227e33c6b7d07f11687385d788017350e3827 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
So far, Only console, http module has been tested. Config file is generated using defconfig, and contains those mandatory options: ``` CONFIG_NET_LOCAL=y CONFIG_NET_TCPBACKLOG=y CONFIG_PTHREAD_MUTEX_TYPES=y CONFIG_RR_INTERVAL=100 CONFIG_SCHED_LPWORKPRIORITY=176 ``` Build flags are relying on mcpu flags. More IO modules to be supported next. Relate-to: rzr/webthing-iotjs#3 Change-Id: Ib44227e33c6b7d07f11687385d788017350e3827 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
nucleo-144: Mount sysfs for ifconfig for f767-netnsh/defconfig Even if ifconfig is working to set IP, it will not work to display NICs (without args) Change-Id: I62e0b2b5517620c5bc2dd4d3f5bf6f1e0f329d44 Relate-to: rzr/webthing-iotjs#3 Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
More PWMs and multi channels support may be investigated and added later. It was tested on nucleo-f767zi with those features enabled in configuration: ``` CONFIG_EXAMPLES_PWM=y CONFIG_PWM=y CONFIG_STM32F7_TIM1=y CONFIG_STM32F7_TIM1_PWM=y CONFIG_STM32F7_TIM2=y (...) CONFIG_STM32F7_TIM4_PWM=y ``` Change-Id: I08ebd4a538d15661788a0a54c2113ad767f22747 Bug: https://bitbucket.org/nuttx/nuttx/issues/153 Relate-to: rzr/webthing-iotjs#3 Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/862 Signed-off-by: Philippe Coval <p.coval@samsung.com>
stm32f7: Add basic PWM support to nucleo-144 board More PWMs and multi channels support may be investigated and added later. It was tested on nucleo-f767zi with those features enabled in configuration: ``` CONFIG_EXAMPLES_PWM=y CONFIG_PWM=y CONFIG_STM32F7_TIM1=y CONFIG_STM32F7_TIM1_PWM=y CONFIG_STM32F7_TIM2=y (...) CONFIG_STM32F7_TIM4_PWM=y ``` Change-Id: I08ebd4a538d15661788a0a54c2113ad767f22747 Bug: https://bitbucket.org/nuttx/nuttx/issues/153 Relate-to: rzr/webthing-iotjs#3 Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/862 Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
As support is "experimental", so far it's an annex of SMT32F4. Note for later, once support has been validated for all modules it would make sense to move contents to specific file for STM32F7. Relate-to: rzr/webthing-iotjs#3 Change-Id: I22f6552b00b86444986c4d5c652f15ff73509b90 Signed-off-by: Philippe Coval <p.coval@samsung.com>
So far, Only console, http module has been tested. Config file is generated using defconfig, and contains those mandatory options: ``` CONFIG_NET_LOCAL=y CONFIG_NET_TCPBACKLOG=y CONFIG_PTHREAD_MUTEX_TYPES=y CONFIG_RR_INTERVAL=100 CONFIG_SCHED_LPWORKPRIORITY=176 ``` Build flags are relying on mcpu flags. More IO modules to be supported next. Relate-to: rzr/webthing-iotjs#3 Change-Id: Ib44227e33c6b7d07f11687385d788017350e3827 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
As support is "experimental", so far it's an annex of SMT32F4. Note for later, once support has been validated for all modules it would make sense to move contents to specific file for STM32F7. Relate-to: rzr/webthing-iotjs#3 Change-Id: I22f6552b00b86444986c4d5c652f15ff73509b90 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
More modules may be added once tested Relate-to: rzr/webthing-iotjs#3 Change-Id: Ic94115bbaba33947f5fb0566adcbea5f028270b1 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
nucleo-144: Add romfs support Image was generated using genromfs tool. It was successfuly tested on Nucleo-f767zi. Source code is aligned to STM32F4-discovery board with latest fixes (2bfbc23251ef7328b2f1d34a65a47949f08a741c). Thanks-to: Tomasz Wozniak <t.wozniak@samsung.com> Relate-to: https://bitbucket.org/nuttx/nuttx/pull-requests/494/generic-auto-romfs/diff Relate-to: rzr/webthing-iotjs#3 Change-Id: I8dd7e03172307de76d7c0c2c32769683c1298f64 Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/899 Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
Preprocessor can't use == on strings", so new symbols are introduced to test configurations at build time. Note, this mistake was harmless because there weren't any spefic parts among boards, but this will change in upcoming change. Change-Id: I45d87cccc086af05661eaf7b762a4a0274fb2ede Relate-to: rzr/webthing-iotjs#3 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Preprocessor can't use == on strings", so new symbols are introduced to test configurations at build time. Note, this mistake was harmless because there weren't any spefic parts among boards, but this will change in upcoming change. Change-Id: I45d87cccc086af05661eaf7b762a4a0274fb2ede Relate-to: rzr/webthing-iotjs#3 Forwarded: jerryscript-project#1892 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Preprocessor can't use == on strings", so new symbols are introduced to test configurations at build time. Note, this mistake was harmless because there weren't any spefic parts among boards, but this will change in upcoming change. Change-Id: I45d87cccc086af05661eaf7b762a4a0274fb2ede Relate-to: rzr/webthing-iotjs#3 Forwarded: #1892 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Aligned to configuration of NuttX: GPIO_ADC1_IN3 nuttx/configs/nucleo-144/src/stm32_adc.c (nuttx-7.21-298-gc67b807f43) More pins/channels may be configured later. Change-Id: I5407e6b9b91eaa8570713d0331f786441ce0c649 Relate-to: rzr/webthing-iotjs#3 Forwarded: https://github.com/pando-project/iotjs/pull/ IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Aligned to configuration of NuttX: GPIO_ADC1_IN3 nuttx/configs/nucleo-144/src/stm32_adc.c (nuttx-7.21-298-gc67b807f43) More pins/channels may be configured later. Change-Id: I5407e6b9b91eaa8570713d0331f786441ce0c649 Relate-to: rzr/webthing-iotjs#3 Forwarded: jerryscript-project#1894 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Aligned to configuration of NuttX: GPIO_ADC1_IN3 nuttx/configs/nucleo-144/src/stm32_adc.c (nuttx-7.21-298-gc67b807f43) More pins/channels may be configured later. Change-Id: I5407e6b9b91eaa8570713d0331f786441ce0c649 Relate-to: rzr/webthing-iotjs#3 Forwarded: jerryscript-project#1894 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Aligned to configuration of NuttX: GPIO_ADC1_IN3 nuttx/configs/nucleo-144/src/stm32_adc.c (nuttx-7.21-298-gc67b807f43) More pins/channels may be configured later. Also handle difference per processors (this could be aligned in NuttX codebase). Change-Id: I5407e6b9b91eaa8570713d0331f786441ce0c649 Relate-to: rzr/webthing-iotjs#3 Forwarded: jerryscript-project#1894 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
Aligned to configuration of NuttX: GPIO_ADC1_IN3 nuttx/configs/nucleo-144/src/stm32_adc.c (nuttx-7.21-298-gc67b807f43) More pins/channels may be configured later. Also handle difference per processors (this could be aligned in NuttX codebase). Change-Id: I5407e6b9b91eaa8570713d0331f786441ce0c649 Relate-to: rzr/webthing-iotjs#3 Forwarded: #1894 IoT.js-DCO-1.0-Signed-off-by: Philippe Coval p.coval@samsung.com
stm32f7: Add GPIO driver Code is inspired from stm32f3discovery and nucleo-l476rg platforms. It was tested on Nucleo-F767ZI PB2 (@ CN12: 12th from top on right) using: gpio -o 1 /dev/gpout1 gpio -o 0 /dev/gpout1 More insight at: https://github.com/rzr/webthing-iotjs/wiki/MCU# Relate-to: rzr/webthing-iotjs#3 Change-Id: I01e5c7d28c175458d3fd2ecf63c139333c22eb0a Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/ Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
It was tested on Intel edison on PWM0 but GPIO12 must be manually configured first ```chip=0 id=0 gpio=12 echo $gpio | sudo tee /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo 0 | sudo tee /sys/class/gpio/gpio$gpio/value sudo cat /sys/kernel/debug/gpio_debug/gpio$gpio/current_pinmux # mode0 echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmuxsh ``` More/Better gpio drivers maybe used later, 'pwm' one was used here as base for webthing-iotjs. Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 but GPIO12 must be manually configured first ```chip=0 id=0 gpio=12 echo $gpio | sudo tee /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo 0 | sudo tee /sys/class/gpio/gpio$gpio/value sudo cat /sys/kernel/debug/gpio_debug/gpio$gpio/current_pinmux # mode0 echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmuxsh ``` More/Better gpio drivers maybe used later, 'pwm' one was used here as base for webthing-iotjs. Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 but GPIO12 must be manually configured first ```chip=0 id=0 gpio=12 echo $gpio | sudo tee /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo 0 | sudo tee /sys/class/gpio/gpio$gpio/value sudo cat /sys/kernel/debug/gpio_debug/gpio$gpio/current_pinmux # mode0 echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmuxsh ``` More/Better gpio drivers maybe used later, 'pwm' one was used here as base for webthing-iotjs. Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 but GPIO12 must be manually configured first ```chip=0 id=0 gpio=12 echo $gpio | sudo tee /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo 0 | sudo tee /sys/class/gpio/gpio$gpio/value sudo cat /sys/kernel/debug/gpio_debug/gpio$gpio/current_pinmux # mode0 echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmuxsh ``` More/Better gpio drivers maybe used later, 'pwm' one was used here as base for webthing-iotjs. Relate-to: #3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 but GPIO12 must be manually configured first ```chip=0 id=0 gpio=12 echo $gpio | sudo tee /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo 0 | sudo tee /sys/class/gpio/gpio$gpio/value sudo cat /sys/kernel/debug/gpio_debug/gpio$gpio/current_pinmux # mode0 echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmuxsh ``` More/Better gpio drivers maybe used later, 'pwm' one was used here as base for webthing-iotjs. Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 but GPIO12 must be manually configured first ```chip=0 id=0 gpio=12 echo $gpio | sudo tee /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo 0 | sudo tee /sys/class/gpio/gpio$gpio/value sudo cat /sys/kernel/debug/gpio_debug/gpio$gpio/current_pinmux # mode0 echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmuxsh ``` More/Better gpio drivers maybe used later, 'pwm' one was used here as base for webthing-iotjs. Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 GPIO12 must be manually configured first using: ```sh gpio=12 echo $gpio | sudo tee -a /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmux ``` More insights at: https://github.com/rzr/webthing-iotjs/wiki/Actuator Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 GPIO12 must be manually configured first using: ```sh gpio=12 echo $gpio | sudo tee -a /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmux ``` More insights at: https://github.com/rzr/webthing-iotjs/wiki/Actuator Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
It was tested on Intel edison on PWM0 GPIO12 must be manually configured first using: ```sh gpio=12 echo $gpio | sudo tee -a /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmux ``` More insights at: https://github.com/rzr/webthing-iotjs/wiki/Actuator Relate-to: #3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
STM32 support is provided with Nucleof767ZI see sample webthing:
Released in:
I am closing this issue, please open new bugs for related issues or wishes A couple of suggestion here: rebase on TizenRT, support BLE, target more boards. More more detail to come at : https://github.com/rzr/webthing-iotjs/wiki/MCU Thanks for your patience |
It was tested on Intel edison on PWM0 GPIO12 must be manually configured first using: ```sh gpio=12 echo $gpio | sudo tee -a /sys/class/gpio/export echo out | sudo tee /sys/class/gpio/gpio$gpio/direction echo mode1 | sudo tee /sys/kernel/debug/gpio_debug/gpio${gpio}/current_pinmux ``` More insights at: https://github.com/rzr/webthing-iotjs/wiki/Actuator Relate-to: rzr/webthing-iotjs#3 Change-Id: I6f587a840e8c429d91ba2491e7cddfdfab66bf4b Signed-off-by: Philippe Coval <p.coval@samsung.com>
stm32f4discovery: Fix declaration statement Column was missing from cc6b127 Change-Id: Ia0ec2aba809804bb44ffcba049b605c1f430d463 Relate-to: rzr/webthing-iotjs#3 Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/898/stm32f4discovery-fix-declaration-statement/diff Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
nucleo-144: Add romfs support Image was generated using genromfs tool. It was successfuly tested on Nucleo-f767zi. Source code is aligned to STM32F4-discovery board with latest fixes (2bfbc23251ef7328b2f1d34a65a47949f08a741c). Thanks-to: Tomasz Wozniak <t.wozniak@samsung.com> Relate-to: https://bitbucket.org/nuttx/nuttx/pull-requests/494/generic-auto-romfs/diff Relate-to: rzr/webthing-iotjs#3 Change-Id: I8dd7e03172307de76d7c0c2c32769683c1298f64 Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/899 Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
stm32f7: Add GPIO driver Code is inspired from stm32f3discovery and nucleo-l476rg platforms. It was tested on Nucleo-F767ZI PB2 (@ CN12: 12th from top on right) using: gpio -o 1 /dev/gpout1 gpio -o 0 /dev/gpout1 More insight at: https://github.com/rzr/webthing-iotjs/wiki/MCU# Relate-to: rzr/webthing-iotjs#3 Change-Id: I01e5c7d28c175458d3fd2ecf63c139333c22eb0a Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/ Signed-off-by: Philippe Coval <p.coval@samsung.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
Are there any other STM32 boards to be considered ? STM32MP1 should easy to port using: https://github.com/STMicroelectronics/meta-st-stm32mp/commits/zeus Please let me know at: https://community.st.com/s/feed/0D50X0000ArV5ykSQC Regards |
Our financial instruments use STM32F (and we're trying to integrate STM32L.) The secure signing devices would benefit from this framework, but it is not supported on any STM32 MCU.
Please port IoT WoT to the STM32 (for example STM32F205RET6.)
The text was updated successfully, but these errors were encountered: