users@lists.zephyrproject.org | How to use TRACEDATA pins as GPIO -

Rodrigo Peixoto <rodrigopex@...>

#1058

Hi,

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.

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

Rodrigo Peixoto <rodrigopex@...>

#1060

Thank you Vinayak.

For now, I will change the HAL file to solve that. When you have news about it please let me know.

Best regards,
Rodrigo Peixoto

Show quoted text

On Mon, 3 Sep 2018 at 05:04 Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:

Hi Rodrigo,

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.

Regards,

Vinayak

From: users@... <users@...> on behalf of Rodrigo Peixoto <rodrigopex@...>
Sent: Sunday, September 2, 2018 4:54:59 PM
To: users@...
Subject: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard

Hi,

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.

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

--

Rodrigo Peixoto
Co-founder and Technical guru

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex

.

Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>

#1063

Hi Rodrigo,

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.

Regards,

Vinayak

Show quoted text

From: users@... <users@...> on behalf of Rodrigo Peixoto <rodrigopex@...>
Sent: Sunday, September 2, 2018 4:54:59 PM
To: users@...
Subject: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard

Hi,

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.

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...>

#1064

Hi Rodrigo,

The Trace Port Interface Unit is ARM supplied component in nRF52, could you please open a GitHub issue asking for support of the same in Zephyr OS?

Also, an explain of its use in your applications requirement.

We can then better co-ordinate with the community in adding a ARM feature support and its support in nRF52 series.

Regards,

Vinayak

Show quoted text

From: Rodrigo Peixoto <rodrigopex@...>
Sent: Monday, September 3, 2018 11:59:19 AM
To: Chettimada, Vinayak Kariappa
Cc: users@...; Głąbek, Andrzej; Cufi, Carles
Subject: Re: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard

Thank you Vinayak.

For now, I will change the HAL file to solve that. When you have news about it please let me know.

Best regards,
Rodrigo Peixoto

On Mon, 3 Sep 2018 at 05:04 Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:

Hi Rodrigo,

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.

Regards,

Vinayak

From: users@... <users@...> on behalf of Rodrigo Peixoto <rodrigopex@...>
Sent: Sunday, September 2, 2018 4:54:59 PM
To: users@...
Subject: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard

Hi,

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.

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

--

Rodrigo Peixoto
Co-founder and Technical guru

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex

.

Rodrigo Peixoto <rodrigopex@...>

#1065

Vinayak,

That is ok. I will open the issue on github.

After removing the code directly on the system_nrf52.c the board had stopped to answer the nrfjprog. I thought that was independent of the tracedata, but it seems to be dependent. Any idea of how can I recover the board? It is not responding on the jlink interface.

Rodrigo Peixoto

Co-founder and Technical advisor

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

Em seg, 3 de set de 2018 às 09:29, Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> escreveu:

Hi Rodrigo,

The Trace Port Interface Unit is ARM supplied component in nRF52, could you please open a GitHub issue asking for support of the same in Zephyr OS?

Also, an explain of its use in your applications requirement.

That is ok.

We can then better co-ordinate with the community in adding a ARM feature support and its support in nRF52 series.

Regards,

Vinayak

From: Rodrigo Peixoto <rodrigopex@...>
Sent: Monday, September 3, 2018 11:59:19 AM
To: Chettimada, Vinayak Kariappa
Cc: users@...; Głąbek, Andrzej; Cufi, Carles
Subject: Re: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard

Thank you Vinayak.

For now, I will change the HAL file to solve that. When you have news about it please let me know.

Best regards,
Rodrigo Peixoto

On Mon, 3 Sep 2018 at 05:04 Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> wrote:

Hi Rodrigo,

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.

Regards,

Vinayak

From: users@... <users@...> on behalf of Rodrigo Peixoto <rodrigopex@...>
Sent: Sunday, September 2, 2018 4:54:59 PM
To: users@...
Subject: [Zephyr-users] How to use TRACEDATA pins as GPIO - #nrf52832 #customboard

Hi,

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.

Best regards,

Rodrigo Peixoto

Co-founder and Technical advisor

+55 (82) 98144-8585

http://ayna.tech | Skype: rodrigopex

--

Rodrigo Peixoto
Co-founder and Technical guru

+55 (82) 98144-8585
http://ayna.tech | Skype: rodrigopex

.