RTOS/CC1310: cc1310 resetting continuously using sdk collector sensor project 0 codes

ali burhan

Part Number: CC1310

Tool/software: TI-RTOS

we used the example of tirtos sensor collector in the CC1310 launchpad with no problem. then we used another card with the same circuit but some changes in input output pins of the processor. the program keeps on resetting showing something like this continuously:

TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.TI Collec.

we removed a lot of connected pins like buttons leds but still the processor is keep resetting. because of that the debug program gives error. so we can not debug in code composer studio.

any suggestion for tracking the resetting cause is appreciated.

over 7 years ago

0 Hector_r over 7 years ago

TI__Genius 12415 points

Hi,
Have you tried checking the voltage level in the reset pin of your custom board?

0 ali burhan over 7 years ago in reply to Hector_r

Intellectual 290 points

yes we checked the voltage level that feeds the processor it was below 3 v but then we removed some components and resolved to be exactly 3 v entering the processor. but the problems still exists the processer keeps on resetting itself

0 ali burhan over 7 years ago in reply to Hector_r

Intellectual 290 points

any other suggestions?

0 ali burhan over 7 years ago

Intellectual 290 points

we have this message received in the console while debugging:

Cortex_M3_0: Error: (Error -11e2e.ti.com/.../775174 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.903.2).

0 Hector_r over 7 years ago in reply to ali burhan

TI__Genius 12415 points

Have you tried setting up a breakpoint before the reset happens and step through the code to try to find the place where the reset is getting triggered?

0 ali burhan over 7 years ago in reply to Hector_r

Intellectual 290 points

it enters debug then after getting inside BIOS_start() it gives the error can not access the DAP
lately we could read the register that give the reason of reset it says a clock loss

0 TER over 7 years ago in reply to ali burhan

TI__Guru**** 317180 points

It could sound like a hardware issue.
Could you try to run the following examples found in the SDK:
- empty
- pinstandby
- rfcarrierwave

and see which ones runs as expected.

I assume "another card with the same circuit " means that you have a custom board. If that is the case I can do a quick schematic + layout review to see if I can see something that could explain what you are seeing.

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

schematic.pdf

this is the schematic we used.

I will try the examples you said and reply again.

0 TER over 7 years ago in reply to ali burhan

TI__Guru**** 317180 points

The schematic looks ok from a RF view.

Do you have the exact part number for Y101?

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

TSX-3225 24.0000MF20G-AC0
part number of Y101

0 TER over 7 years ago in reply to ali burhan

TI__Guru**** 317180 points

The xtal looks good and should not cause any issue.

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

ok we tried the examples you said.

for empty and pinstandby we assume it's working normally we don't have a led but we saw the 32 khz clock working without resetting and 24Mhz clock not working because no radio was used in these two programs.

for the rfcarrierwave, everything seems normal, 32 Khz clock works fine without resetting. 24Mhz also works fine without any problem.

0 TER over 7 years ago in reply to ali burhan

TI__Guru**** 317180 points

I get a email when something is posted and I see that the content of the email is different from what is shown in the post. It looks like the first concussion was that the 24 MHz xtal did not work and then you changed it to works. I assume you also get a RF signal on the output?

Do you know why the functionality changed while testing?

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

actually there was a problem with the oscilloscope so we tested it with another one.

there was no problem works fine.

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

we also saw the RF signal on the output.

still the collector sensor project 0 example resets the board.

0 TER over 7 years ago in reply to ali burhan

TI__Guru**** 317180 points

Have you tried to monitor the current consumption, VDDS, VDDR and tried to correlate this with when then you get a reset? Have you stepped through the program and tried to see exactly which line that causes a reset? Not sure why the 24 MHz xosc should be running in one example and stop working in another example.

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

we just found out that our board draws more current consumption than the launchpad board:
launchpad: 20 mA
our board: 31 mA

VDDS and VDDR are the same in launchpad and our board.

we can not know exactly which line: when it goes inside BIOS_start() funcion it starts resetting.

we went through the schematic for any component that may cause the upnormal current consumption. but we didn't find anything that might draw such current.

0 TER over 7 years ago in reply to ali burhan

TI__Guru**** 317180 points

Are you in TX when measuring 31 mA? If so, the current consumption difference could be caused by a different antenna that is not perfect 50 ohm.

Did you measure the current and voltage as a function of time?

BIOS_start() just start TI-RTOS. You should try to set a breakpoint in the first thread that is started to see more of the program flow.

0 ali burhan over 7 years ago in reply to TER

Intellectual 290 points

yes in the third example (rfCarrierWave)the card is transmitting continuously, the RF signal can be seen.

actually that is a good point about the different antenna, we are using coated copper wire, and the launchpad is within the pcb.

the important question might that be a reason for the cpu to reset it self because of the reflected impedence from the antanna matching circuit.

for the third example (rfCarrierWave), the launchpad is continuously consuming 20mA and our board is consuming 27 mA then changes to 31 mA and stays there. the voltage is fixed to 3 volts. I don't know if that answers your question.

I will write again when I get other information.

0 Katie Pier over 7 years ago in reply to ali burhan

TI__Guru* 83431 points

Hi Ali,

Any update? Are things working well now?

Regards,
Katie

Sub-1 GHz

Sub-1 GHz forum

RTOS/CC1310: cc1310 resetting continuously using sdk collector sensor project 0 codes