|
|
| Re: Success ... but more questions [message #1844481 is a reply to message #1844475] |
Tue, 14 September 2021 23:49  |
 Anne Ranch
Messages: 57
Registered: October 2020 |
Member |
|
|
Eugene Tarassov wrote on Tue, 14 September 2021 17:04If you enter both Local and Remote file path, TCF will copy (download) the file from Local to Remote every time you launch the debug session.
> Should I be able to "find" -name "*BASE*" somewhere on my RPi?
No, because you entered "test" as the Remote file name, not "*BASE*".
> any path, even "/" empty
I'm not sure what you mean. Remote file path cannot be a directory, it should be a file.
OK, let;s recap.
There are these entries
1. local "file path" ( Debug/BASE_CrossGCC) which is hardly a "path" because it includes the actual file name.
But that works.
2. Remote "file path" which makes no sense because just "/" will enable "run" button and it will execute on the RPi.
3. Then there is a "remote directory" which has option of "default" , and same as above item 2 - the app runs on RPi with default.
The cross linker clearly identifies the object file and I cannot "find" in on the RPi.
Now to make it more interesting - in "TCF debug" configuration I get "TCF process console " and so far I have no idea where does it come from - it is "automatic" . It does "print" all stuff coded ....
And I believe there is "by the way" a note which said that this "TCF process" has to run/ be implemented on the target.
All this makes implementing TCF such hit and miss, but I still believe resolving all of these by giving reasons why - would make Eclipse and TCF a great tool to make Raspberry really shine.
Funny part - this has all been discussed before , but my personal RAM is not that great anymore...
yes, I kept notes ....periodically destroyed by new and "improved " OS
Cheers
|
|
|
Powered by
FUDForum. Page generated in 0.02807 seconds
] 
Search
Help
Register
Login
Home
