Thank you for the infos. I downloaded the datasheet of the EP9302 on the cirrus web page (42 pages) but I found no useful hardware programming description.
Best regards and if you have another better source for a more detailed data sheet then please let me know:)
You need the user’s manual (it’s on the Cirrus page, too). The datasheet mostly describes electrical parameters, while the user’s manual holds the functional description, registers etc.
Right, the EP9302 is special, as there’s no user’s manual for it. You’ll have to look at the user’s manual for the EP9301 and others. The EP9302 is mostly a 9301 with 100/200MHz clocks and MavericCrunch.
You are great. Thank you for the fast help! This is exactly the document I am looking for. Nice document:)
I saw your debugger with very good critics:) Beyond the Olimex-Boards there are some boards available with ethernet but wihtout JTag. Can the openOCD debugger also be used over ethernet and if yes it what cases does it make sense to use the tool?
Thank you very much for your fast response and the help. This is exactly the document I am looking for.
To your OpenOCD. There are some boards available with the EP9302 and an Ethernet interface running Linux. Does it make sensd to use the OpenOCD also in this case and if yes what are the advantages. According to the critics it seems to be a very useful tool:)
@NIeahciM
Very good question. For me this is also an very important question. Maybe we only have to put one compiler switch:)
The OpenOCD requires a JTAG interface to the target, because it’s a very low-level debugging instrument. If you already have Linux running on a board it’s a lot easier to use gdbserver, which uses the OS facilities to control the target application. Gdbserver can be used over serial lines as well as over an Ethernet connection.
Thank you very much for clarifying the use of th OpenOCD tool, interesing!
To the Crunch engine:
EABI (Embedded Application Binary Interface): That sounds as if some deeper knowledge is necessary to use the strength of this controller… Value passing will probably be no problem but assembler coding…
EABI (Embedded Application Binary Interface): That sounds as if some deeper knowledge is necessary to use the strength of this controller… Value passing will probably be no problem but assembler coding…
Not really. On ARM-Linux, you normally still use the "old" ABI. To use the newer EABI you need a kernel with EABI support enabled, a toolchain that supports it, and a userland (libraries, service utilities, etc.) compiled for EABI. Openembedded supports building EABI systems afaik, and Angstrom does this ([http://www.angstrom-distribution.org/](http://www.angstrom-distribution.org/)).