Thank you Vinayak.
toggle quoted messageShow quoted text
For now, I will change the HAL file to solve that. When you have news about it please let me know.
Glad to hear your success with first custom board made to run Zephyr.
You are right, the ENABLE_TRACE in the Nordic external MDK is not a Kconfig option in Zephyr.
This will need a new MDK release to be integrated. I will inform our team regarding this.
From: users@... <users@...> on behalf of Rodrigo Peixoto <rodrigopex@...>
Sent: Sunday, September 2, 2018 4:54:59 PM
Subject: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard
I have developed a custom board based on the nrf52832. Everything is running properly and I am glad to have my first board made to run Zephyr on it.
The only issue I am facing right now is that we have used some pins that are shared with TRACEDATA and I could not see any straightforward way of disabling it on Zephyr. Is there any? I have already disabled the CONFIG_SEGGER_SYSTEMVIEW config on my board
files but it is still being used as TRACEDATA and not as GPIO. I have found the ext/hal/nordic/nrfx/mdk/system_nrf52.c file that has information related to that and says if we define ENABLE_TRACE the pins will be attached to TRACEDATA. I could not find any
point where the ENABLE_TRACE is being defined. I could change the cited file in HAL directly, but I think it is not a sustainable solution.
Any clue on that?
Thank you very much.
Co-founder and Technical advisor
+55 (82) 98144-8585
Co-founder and Technical guru
+55 (82) 98144-8585 http://ayna.tech
| Skype: rodrigopex