Eclipse, HTS, HEW & Target MCU
Up to HEW Target Server (HTS)
I've been looking at the list of potential usage of HTS, and stumbled across Eclipse. So far I'm thinking of usages of Eclipse (and their CDT project) for HTS.
Is there any usages, or wish list ppl want to see?
Cheers,
Hendra
If you could implement a GNU/GCC development platform under Eclipse with CDT, it would be great. You'd have a nice way to manage a project and create build configurations - plus the build process would also be automated.
The way I'd see you using HTS/HEW would be for handling the debugging of your output code. Will all of the hooks HTS provides, it would be possible to create a "virtual" debugging environment in Eclipse (but all the connections and work would be done by HEW/HTS).
For people who really want to work in Eclipse, this might be a usefull thing to have.
Hmm...interesting. Thanks for your idea, I'll think and evaluate the possibilities first. Other thing to consider is I try to avoid if Vis Studio already has that capabilities?
I've modified gdbserver, it translates GDB commands to HEWTargetServer.
Attached code works with SH7203 but after small modifications it should work with all sh family members.
Best regards
Krzysztof
Maybe You are right, but the problem is that most of code is basing on GPL license. In near future I'll try to clean code and make it more general. I also consider adding support for simple JTAG wiggler (Xilinx parallel cable III compatible) replacing E10A emulator. For the time being debugging using wiggler works for SH7619 and SH7750R processors. Adding support for different processors it is only matter of adding particullar ASE stubs. Main drawback of debugging using wiggler is its rather slow data transfers (up to 16 kB/s ) but its really cheap and can give SH familly chance to compete with ARM family which have better free tools support.
Best regards
Krzysztof
Wow, debugging in Eclipse (via HTS) with a parallel port "wiggler" cable...
This is really a unique contribution to the development tools for SH. Bravo! How/where are you getting the ASE stubs? I'd offer to help, but I'm not sure I know what they are...
All SH processors have small special SRAM used by the emulators (eg. E10A). This memory is called ASE RAM and it is the place where emulator software called stub is loaded throuth JTAG. ASE memory can be found at FC000000h for SH2 and SH4, 80000000h for SH2A. When breakpoint is generated processor starts to execute program in ASE memory. The main aim of ASE stub is to provide basic operations for debugger as memory or registers reading/writing and also returning to interrupted program. All communication betwen stub runing on processor and emulator/wiggler is provided by the HUDI (you can find some informations in very old hitachi manuals and even more in ST20 manual). When You have e10a, You can look at orginal Renesas ASE stubs of coure remember that they are protected by copyright laws.
If somebody is interested I can provide some deeper information in this topic. Several years ago I have asked people form Resesas why they don't want to public details on debuging interface of SH family. The answer was very unclear, they explained that the problem is that they can not provide satifactory support. But here in Europe they are going to loose with ARM without good and cheap tools.

