WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Suggestions for remote JTAG debugger  (Read 2792 times)

Offline speedbug78

  • Newbie
  • *
  • Posts: 8
Suggestions for remote JTAG debugger
« on: December 14, 2011, 12:26:22 AM »
First I want to thank the developers of TC, took me forever to find it, but man, its awesome!  I'm doing stuff with it that I have been unable to do with any other distro I've used!

The setup:  Neoware EON-4000S thin client, ~300 Mhz geode, 180MB ram, 4GB CF, parallel port JTAG wiggler, LPC1769 ARM Cortex M3 dev. board (LPCXpresso), compiled copy of OpenOCD, ssh server

The goal:  Recycle some old hw I have laying around (I love making something useful out of old stuff) into a dirt cheap ARM development station that I can plug into the net and access from anywhere.  This lets me use my powerful computers for the hard stuff, and I get to use the oldish hardware with good I/O (parallel ports, 232 ports) for great uC interfacing.

ToDo: Install some kind of firewall before plugging into the net, maybe install an ARM cross compiler for emergency builds or small apps.

Questions:
- It would be cool if the thin client served a pre-configured cross compiler to whatever computer I'm using to access it just in case I forget to bring one along, but I haven't thought of a great way to do this, ideas?

- What great tools/ideas am I missing that would make this setup even better?

- What web browser should I use for this level of hw?  I tried icecat since I've previously used iceweasel and liked it, but it was very slow.  From my searches maybe dillo?  Most of the time I'll probably boot TC in text mode, but for setup or changing something on the thin client the gui/web browser is handy.

<big jk> anyone know how to encrypt my connection so I can protect my super secret CLOSED source code ;) </big jk>

Again a big thanks to the developers, while TC hasn't been trouble-free it is still an incredible OS.

Admins:  After reading the posting rules, I was left a bit confused about where posts like this should go.  If it should be in another section, or another forum all together, please move or suggest somewhere else for me to go, thanks.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11696
Re: Suggestions for remote JTAG debugger
« Reply #1 on: December 14, 2011, 12:43:30 AM »
Hi speedbug78
180Mb isn't a lot of RAM to work with. You could try Opera9. If that doesn't cut it, I think  Lynx  and
Links-cli  are both text based browsers.

Offline speedbug78

  • Newbie
  • *
  • Posts: 8
Re: Suggestions for remote JTAG debugger
« Reply #2 on: December 14, 2011, 01:58:34 AM »
Hi speedbug78
180Mb isn't a lot of RAM to work with. You could try Opera9. If that doesn't cut it, I think  Lynx  and
Links-cli  are both text based browsers.

Thanks for the suggestions, I just tried Opera9 but felt that I was in the gray area on their terms so I didn't accept them, Lynx doesn't seem to want to start for me (TC 4.1, lynx http://www.google.com), but I may be doing something wrong?  Dillo seems to be working with acceptable speed at this point (about 8 secs to start).
« Last Edit: December 14, 2011, 02:12:57 AM by speedbug78 »

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11049
Re: Suggestions for remote JTAG debugger
« Reply #3 on: December 14, 2011, 04:20:26 AM »
How are you going to access it? SSH is encrypted by default. For the firewall see iptables.tcz.

For serving a cross-compiler, what more is there than to keep a tarball of one on it? ;)
If you access via SSH, you can scp it to your end. If some other way, we have many http and ftp servers, tftpd is available in the base, etc.
The only barriers that can stop you are the ones you create yourself.

Offline speedbug78

  • Newbie
  • *
  • Posts: 8
Re: Suggestions for remote JTAG debugger
« Reply #4 on: December 14, 2011, 09:54:54 PM »
How are you going to access it? SSH is encrypted by default. For the firewall see iptables.tcz.

For serving a cross-compiler, what more is there than to keep a tarball of one on it? ;)
If you access via SSH, you can scp it to your end. If some other way, we have many http and ftp servers, tftpd is available in the base, etc.

As far as connecting to it, OpenOCD supports connections via telnet, RPC, and/or a direction connection with GDB, though I might use ssh too, we'll have to see how things pan out.  I saw that iptables had been built for TC, haven't used it before, so I'll have to dig up the time to play with it.

As far as the cross-compiler goes, I guess its mostly a decision of how ready-made I make it.  Do I have it all configured and ready to go, which tends to limit what kind of machine I can extract it to, or do I just put all the building blocks on there so I can build it for almost anything (a lot more time consuming).  Maybe I'll just have to decide on my own, but people with experience tend to have insight on this stuff that's worth considering.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11696
Re: Suggestions for remote JTAG debugger
« Reply #5 on: December 14, 2011, 10:48:03 PM »
Hi speedbug78
There's nothing to stop you from having more than one pre-configured cross compiler. Use
compressed tarballs for Linux platforms. If you want to download to Windows, you can store
those in zip format.



Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11049
Re: Suggestions for remote JTAG debugger
« Reply #6 on: December 15, 2011, 05:59:51 AM »
Yep, having one 32-bit and one 64-bit tarball should be enough (assuming you still develop on x86 :)).
The only barriers that can stop you are the ones you create yourself.