Created
December 8, 2017 08:25
-
-
Save four0four/680e1fa70e7c216baac2afbd459d03d8 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
source [find cpu/arc/arcompact.tcl] | |
source [find cpu/arc/em.tcl] | |
set _CHIPNAME arc600 | |
set _TARGETNAME $_CHIPNAME.cpu | |
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -expected-id 0x200024b1 | |
target create $_TARGETNAME arc600 -chain-position $_TARGETNAME | |
arc jtag wait-until-write-finished on | |
$_TARGETNAME configure -event reset-assert "arc_arcompact_reset $_TARGETNAME" | |
arc_arcompact_init_regs |
@dossalab "I managed to program thit chip using just FT2232H JTAG and some python code to take binary and send it to the controller. " Would you mind sharing that python code please?
I found something, even though it's most likely an initial version. It connects through telnet to a running OpenOCD instance and sends direct reads and writes and talks to the controller... I've given you access in private but if it works fine I'll happily disclose it for the public.
You'll need the correct openocd script with the fix I mentioned before.
The way to go would be to write the 'correct' driver for OpenOCD. May be that's the time....
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@dossalab
"I managed to program thit chip using just FT2232H JTAG and some python code to take binary and send it to the controller. "
Would you mind sharing that python code please?