A router subpath could not be accessed

Vladimir,

What target/emulator are you using? You might try running the fsclean.exe utility in ccs_base/common/bin and see if that changes anything.

Thanks,
Mark

I am using CC2640.
I do not see fsclean.exe in directory "ccs_base/common/bin". In that directory, I have "ti_targetdb_parser.dll", "xerces-c_2_5_0.dll" and "xerces-c_2_8.dll".

Sorry, there should be a fsclean.bat script that you can run in ccs_base/common/bin. Do you have it?

I'm unable to reproduce the issue with Emulation package 6.0.14.0 and a CC2650 device (I don't seem to have CC2640 handy). Can you share your target configuration?

Thanks,
Mark

1) How can I get target configuration? Which information you need?

2) I checked at my colleague - he also does not have "fsclean"

Glad to hear!

Thanks,

Mark

Hey,
we are currently encountering the same problem with the same error massage when trying to program the chip. Which pin alignment was faulty?
The Jtag connection? or probably the footprint on the PCB?
i hope you can help us, since this is almost 1 year old.
edit: Okay as i noticed the error message is not quite the same... we are getting:

Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. (Emulation package 6.0.14.5)

greetings,

philipp

Hello Philipp,

have you solved the problem of Error connecting to the target:(Error-241@0x0). I am also facing same error. 

I am waiting for a positive reply from your side.

Thanks in advance!

Hi,

I'm facing a similar problem.

I built a prototype using CC2640 and started to play with it, not paying much attention on the ESD and other little glitches that may occur while performing such debug tasks on an open circuit laying on the desk.

After couples days working fine, I now get an error message when trying to program the device:

Error connecting to the target:(Error -242 @ 0x0)
A router subpath could not be accessed.
The board configuration file is probably incorrect.
(Emulation package 6.0.228.0)

I do have a second prototype which I still can program with no problem (unfortunately I can't use that particular one for my testing)

Another important point, is hat the devpack I was using when the programming stopped working is now dead (no more recognized as a USB device). It was an old rev 1.2.0 one.

I suspect something wrong in the JTAG connection, since everything is working fine on the CC2640. Just, I'm no more able to upload a new firmware.

Is there something particular I should check before trying to replace the unit (since this is not an easy task!)

Thanks

JYL

Do you mean that the DevPack is dead now so that there is no way to program any CC2640 boards on your hand?
Can you post the circuit connections between DevPack and your custom board?

Hi Robert,

This particular DevPack is now definitely dead. No way to do anything with it. It is even no more recognized on USB port and what seems to be the LDO (next to the USB connector) gets hot.
I do have by chance a second unit, which can program other devices, but not the prototype on which I'm currently working.
The circuit connection uses the 10 points header and is completely similar to what is done with the sensor tag:
1: VDD
3,5,9: GND
7: NC
2: TMS
4:TCK
6:TDO
8:TDI
10: Reset\

Best regards
JYL

So I suppose you connect it to J2 of DevPack. The VDD pin in J2 is actually not used (not connected) in DevPack. So, it doesn't make sense for the LDO to get hot. Do you solder the custom board manually? I think you have to check any unexpected shortage between pins on your boards.

Btw, is it possible that you accidentally short DevPack with custom board since the DevPack is not protected by any housing. It is bare.

Indeed, my prototype was connected through J2 connector of DevPack.
I know VDD is left open on DevPack, so I suspect something else weird happened.
It's not impossible that a short circuit appeared somewhere during the debug phase.
The board has not been soldered manually, but using standard reflow soldering.
I'm afraid it's unfortunately time for me to change the CC2640...
Thanks
JYL

I just think of another possibility. During debugging with DevPack, did you use oscilloscope to probe custom board and the ground clip of oscilloscope is not connected to GND but connected to a "non-GND" pin? This will cause a so-called "grounding loop potential" and something in the loop will "burn" due to unexpected voltage difference between grounds. Since DevPack is not an isolated debugger, this is very likely to happen.

If this is the case then I have to say you are very lucky. Either custom board, DevPack or the PC connected will get damaged in this case. If it is the PC get damaged then you are in big trouble.

Hello Robert,
I am also having a similar problem with CCS6 but on my sid this is with a launchpad CC1310 with XDS 110 on it./
When I try to test the connection I get this error messsage:

"Error connecting to the target:
(Error -242 @ 0x0)
A router subpath could not be accessed.
The board configuration file is probably incorrect.
(Emulation package 6.0.14.5)
"

Hi user4243526,

I'm also facing a similar problem like you.

But I solved this problem today..

In target configuration, you must select right JTAG, SWD, cJTAG mode.
When i select cJTAG 4-pin standart mode, the problem is solved. 

Hi Mehmet Kucukgoz,

Thank you so much, its working.

what 's pin alignment ,i don't understand clear....

Hi user4850651,

For my custom design board : i connected TMS,TCK,TDI,TDO,RESET and GND pins; it worked.

Hello Mehmet,

I'm really glad you posted this answer, because I have been tearing my hair out for almost a week working on this. I am attempting to port a BLE STACK 2.0 project to 2.2.1, and in the process an update to CCS upgraded the firmware on my XDS110 debugger. This in turn apparently reset the jTAG connection mode and prevented me from loading code on to my custom board that had previously been working perfectly fine.

I know this probably isn't the proper forum, but shame on TI for changing settings like this on a software upgrade! I completely blew out my TI CCS installation, reinstalled everything, and really hoped that would solve my problem, but it didn't. It took scouring the forums to find someone nice like Mehmet that had the same problem in order for me to fix it. I know TI has a tough job supporting so many microcontrollers from a single IDE, but my entire experience with CCS and the code breaking changes on every upgrade of BLE STACK has really made me reconsider their products.

If I had the choice in the future, I'd stay far away from TI and CCS if it were up to me.

Anyways, thanks Mehmet!

-Ben

Hello

now I had met  the same problem as you

could you give me some explanation  of pin alignment? I dot not understand this.

Thank you in advance.

BRS,

Meng