README.Purple 1.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. Installation Instructions:
  2. --------------------------
  3. 1. Put the s2 switch into the following position:
  4. Off On
  5. ------
  6. |x |
  7. | x|
  8. |x |
  9. | X|
  10. ------
  11. Put the s3 switch into the following position:
  12. Off On
  13. ------
  14. | x |
  15. | x |
  16. | x|
  17. | x|
  18. ------
  19. Put the s4 switch into the following position:
  20. Off On
  21. ------
  22. |x |
  23. |x |
  24. |x |
  25. |x |
  26. |x |
  27. | x|
  28. | x|
  29. |x |
  30. ------
  31. 2. Connect to the serial console and to the BDI. Power on. On the
  32. serial line, you should see:
  33. PURPLE@1.2>
  34. 3. Type '8'. No echo will be displayed. In response, you should get:
  35. 7A(pass)
  36. 4. From BDI, enter command:
  37. mmw 0xb800d860 0x0042c7ff
  38. 5. Then, from BDI:
  39. erase 0xB0000000
  40. erase 0xB0008000
  41. erase 0xB000C000
  42. erase 0xB0010000
  43. erase 0xB0020000
  44. prog 0xB0000000 <u-boot.bin> bin
  45. 6. Power off. Restore the original S2 switch position:
  46. Off On
  47. ------
  48. | x|
  49. | x|
  50. |x |
  51. | X|
  52. ------
  53. Power on. U-Boot should come up.
  54. Implementation Notes:
  55. ---------------------
  56. Due to the RAM/flash bus arbitration problem the suggested workaround
  57. had to be implemented. It works okay. On the downside is that you
  58. can't really check whether 'erase' is complete by polling flash as it
  59. is usually done. Instead, the flash driver simply waits for a given
  60. time and assumes that erase then has passed. This behaviour is
  61. identical to what the VxWorks driver does; also, the same timeout (6
  62. seconds) was chosen. Note that this timeout applies for each erase
  63. operation, i. e. per erased sector.