Hey Nordic! Just wanted to ask if the issues using nrfconnect on apple silicon macs have been resolved, or is it still necessary to run vscode in intel mode?
Where I am supposed to see the output of the printk commands and how to enable it? I got all working but no console output. I can see there is a conditional on CONFIG_LOG_PRINTK but where is the best place to set it?
You should be able to see output from your DK on the nRF Terminal extension for nRF Connect for VS Code. Please note that you will need to set it up with the correct baud rate, etc. in VS code. The nRF terminal marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-terminal should be installed together with the nRF Connect for VS Code extension.
Unfortunately, we can't determine or control what the ESP-IDF extension does with installed nRF Connect SDKs. If there's anything you think we can improve on our side to avoid this, please let us know on DevZone devzone.nordicsemi.com/
May I ask a question about why my VS Code can not provide the keyword "CONFIG_CONSOLE" suggestion like 34:48? There are only few keywords suggestion like "CONFIG_ARM_MPU", "CONFIG_SOC_SERIES_NRF52X", "CONFIG_SOC_NRF52840_QIAA" & "CONFIG_HW_STACK_PROTECTION".
It should work fine to use "CONFIG_CONSOLE". We would need to know more to give the best support. Please raise a DevZone question to our tech support team on DevZone devzone.nordicsemi.com/ describing the issue you are having, which nRF Connect SDK version you are using and other details that might be relevant.
I got this warning after building it: 'tx-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial ordic,nrf-uarte.yaml for node /soc/uart@40002000. 'rx-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial ordic,nrf-uarte.yaml for node /soc/uart@40002000. 'rts-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial ordic,nrf-uarte.yaml for node /soc/uart@40002000. 'cts-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial ordic,nrf-uarte.yaml for node /soc/uart@40002000. Any solution to this?
With updates to the nRF Connect SDK there has been changes to how to configure pins. We recommend checking out the nRF Connect Fundamentals course: academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/
Highly informative and professional.
Thank you for your feedback!
That was super useful, thank you!
Thank you for your feedback!
Very nice video, TNX.
Hey Nordic! Just wanted to ask if the issues using nrfconnect on apple silicon macs have been resolved, or is it still necessary to run vscode in intel mode?
Hey, this has been resolved for VS Code and nRF Connect for Desktop.
@@NordicSemi that is very nice to hear! Thank you very much!
Cant we use these samples straight away in our custom board
We would need additional information to understand what you are asking. Please connect with our tech support team on DevZone devzone.nordicsemi.com/
Where I am supposed to see the output of the printk commands and how to enable it? I got all working but no console output. I can see there is a conditional on CONFIG_LOG_PRINTK but where is the best place to set it?
You should be able to see output from your DK on the nRF Terminal extension for nRF Connect for VS Code. Please note that you will need to set it up with the correct baud rate, etc. in VS code. The nRF terminal marketplace.visualstudio.com/items?itemName=nordic-semiconductor.nrf-terminal should be installed together with the nRF Connect for VS Code extension.
Installing the ESP-IDF VS Code extension broke nRF Connect for me. Was a long night of cleaning everything out.
Unfortunately, we can't determine or control what the ESP-IDF extension does with installed nRF Connect SDKs. If there's anything you think we can improve on our side to avoid this, please let us know on DevZone devzone.nordicsemi.com/
@@NordicSemi just throwing out a caution for other developers. Your ecosystem is very nice.
@@mgancarzjr Thanks for sharing a heads up to others. And we're glad you think our ecosystem is nice.
May I ask a question about why my VS Code can not provide the keyword "CONFIG_CONSOLE" suggestion like 34:48? There are only few keywords suggestion like "CONFIG_ARM_MPU", "CONFIG_SOC_SERIES_NRF52X", "CONFIG_SOC_NRF52840_QIAA" & "CONFIG_HW_STACK_PROTECTION".
It should work fine to use "CONFIG_CONSOLE". We would need to know more to give the best support. Please raise a DevZone question to our tech support team on DevZone devzone.nordicsemi.com/ describing the issue you are having, which nRF Connect SDK version you are using and other details that might be relevant.
I got this warning after building it:
'tx-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial
ordic,nrf-uarte.yaml for node /soc/uart@40002000.
'rx-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial
ordic,nrf-uarte.yaml for node /soc/uart@40002000.
'rts-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial
ordic,nrf-uarte.yaml for node /soc/uart@40002000.
'cts-pin' is marked as deprecated in 'properties:' in C:/ncs/v2.3.0/zephyr/dts/bindings\serial
ordic,nrf-uarte.yaml for node /soc/uart@40002000.
Any solution to this?
With updates to the nRF Connect SDK there has been changes to how to configure pins. We recommend checking out the nRF Connect Fundamentals course: academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/
@@NordicSemi Thank you very much. I've finally figured it out they are now using pinctrl to select the pins.