You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

76 lines
1.8 KiB

  1. Some outstanding issues w.r.t. non-ARM32 targets
  2. ================================================
  3. This file describes outstanding issues w.r.t.
  4. non-ARM32 targets.
  5. Ideas & patches welcome!
  6. Flash drivers
  7. -------------
  8. The flash drivers contain ARM32 code that is used
  9. to execute code on the target.
  10. This needs to be handled in some CPU independent
  11. manner.
  12. The ocl and ecos flash drivers compile the flash
  13. driver code to run on the target on the developer
  14. machine.
  15. The ocl and ecos flash drivers should be unified
  16. and instructions should be written on how to
  17. compile the target flash drivers. Perhaps
  18. using automake?
  19. eCos has CFI driver that could probably be compiled
  20. for all targets. The trick is to figure out a
  21. way to make the compiled flash drivers work
  22. on all target memory maps + sort out all the
  23. little details
  24. 32 vs. 64 bit
  25. -------------
  26. Currently OpenOCD only supports 32 bit targets.
  27. Adding 64 bit support would be nice but there
  28. hasn't been any call for it in the openocd development
  29. mailing list
  30. target support
  31. --------------
  32. target.h is relatively CPU agnostic and
  33. the intention is to move in the direction of less
  34. instruction set specific.
  35. Non-CPU targets are also supported, but there isn't
  36. a lot of activity on it in the mailing list currently.
  37. An example is FPGA programming support via JTAG,
  38. but also flash chips can be programmed directly
  39. using JTAG.
  40. non-JTAG physical layer
  41. -----------------------
  42. JTAG is not the only physical protocol used to talk to
  43. CPUs.
  44. OpenOCD does not today have targets that use non-JTAG.
  45. The actual physical layer is a relatively modest part
  46. of the total OpenOCD system.
  47. PowerPC
  48. -------
  49. there exists open source implementations of powerpc
  50. target manipulation, but there hasn't been a lot
  51. of activity in the mailing list.
  52. MIPS
  53. ----
  54. Currently OpenOCD has a MIPS target defined. This is the
  55. first non-ARM example of a CPU target