Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:artikel:nav_common:jtag_readout_mainboard_flash [Fri. 08.02.2019 13:54]
go4it
en:artikel:nav_common:jtag_readout_mainboard_flash [Fri. 26.07.2019 19:51] (current)
go4it
Line 1: Line 1:
 ====== Readout content of mainboard Flash memory using JTAG ====== ====== Readout content of mainboard Flash memory using JTAG ======
 +
 +<WRAP center round important 100%>
 +OLD CONTENT! SEE GERMAN VERSION!!
 +</​WRAP>​
  
 ===== Using a Segger J-Link probe ===== ===== Using a Segger J-Link probe =====
Line 11: Line 15:
 Download and install the [[https://​www.segger.com/​downloads/​jlink/​|Segger J-Link Toolchain]] in order to use the J-Flash tool. Download and install the [[https://​www.segger.com/​downloads/​jlink/​|Segger J-Link Toolchain]] in order to use the J-Flash tool.
  
-==== Step 1) Connect the probe to the JTAG-interface of the mainboard ====+===== Step 1) Connect the probe to the JTAG-interface of the mainboard ​=====
  
-[[artikel:​nav_common:​jtag_connect_mainboard]]+[[jtag_connect_mainboard]]
  
-==== Step 2) Disable the Radioprocessor watchdog ====+===== Step 2) Disable the Radioprocessor watchdog ​=====
  
 Besides the OMAP there is a NEC V850 MCU working as a central radio processor. It has control of the reset procedure and powers up all internal devices. It also communicates with the software running on the OMAP in a form like heartbeats. If they are missing for some time (20 seconds or so) it will cut the OMAPs power. This happens when the Segger stops the CPU in order to access the external Flash chip connected to it. The time is not enough to read out the whole memory contents of the Flash, just some sectors. Besides the OMAP there is a NEC V850 MCU working as a central radio processor. It has control of the reset procedure and powers up all internal devices. It also communicates with the software running on the OMAP in a form like heartbeats. If they are missing for some time (20 seconds or so) it will cut the OMAPs power. This happens when the Segger stops the CPU in order to access the external Flash chip connected to it. The time is not enough to read out the whole memory contents of the Flash, just some sectors.
Line 23: Line 27:
 If you plan to to more inspections on the system i suggest to solder a Micromatch 14-pos plug onto the pads of the board and use a custom cable for all the signals. If you plan to to more inspections on the system i suggest to solder a Micromatch 14-pos plug onto the pads of the board and use a custom cable for all the signals.
  
-==== Step 3) Setup J-Flash (="​Project"​) ====+===== Step 3) Setup J-Flash (="​Project"​) ​=====
  
 The OMAP5948 is not directly supported by Segger. This is because this chip is custom made for Bosch (aka Blaupunkt) and there is no public information about it. But i know that it is based on the OMAP5912 and is nearly the same. The OMAP5912 had an ARM926EJ-S CPU inside, which is generally supported by Segger :-) The OMAP5948 is not directly supported by Segger. This is because this chip is custom made for Bosch (aka Blaupunkt) and there is no public information about it. But i know that it is based on the OMAP5912 and is nearly the same. The OMAP5912 had an ARM926EJ-S CPU inside, which is generally supported by Segger :-)
Line 31: Line 35:
 {{artikel:​nav_fx:​projectopts_general.jpg?​direct|}} {{artikel:​nav_fx:​projectopts_general.jpg?​direct|}}
  
-=== Setup JTAG settings for the targetdevice ===+==== Setup JTAG settings for the targetdevice ​====
  
 {{artikel:​nav_fx:​projectopts_target-interface_maxspeed.jpg?​direct|}} {{artikel:​nav_fx:​projectopts_target-interface_maxspeed.jpg?​direct|}}
  
-=== Choose the CPU type ===+==== Choose the CPU type ====
  
 Simply choose "​ARM9"​ from the list of CPUs: Simply choose "​ARM9"​ from the list of CPUs:
Line 41: Line 45:
 {{artikel:​nav_nx:​projectopts_mcu.jpg?​direct|}} {{artikel:​nav_nx:​projectopts_mcu.jpg?​direct|}}
  
-=== Choose the right Flash chip ===+==== Choose the right Flash chip ====
  
 Click on "​Select flash device"​ button and choose "​Spansion S29GL256N"​ (32MB) for an FX satnav device: Click on "​Select flash device"​ button and choose "​Spansion S29GL256N"​ (32MB) for an FX satnav device:
Line 51: Line 55:
 {{artikel:​nav_fx:​projectopts_flash-512.jpg?​direct|}} {{artikel:​nav_fx:​projectopts_flash-512.jpg?​direct|}}
  
-=== Some more settings... ===+==== Some more settings... ​====
  
 {{artikel:​nav_fx:​projectopts_production.jpg?​direct|}} {{artikel:​nav_fx:​projectopts_production.jpg?​direct|}}
Line 57: Line 61:
 {{artikel:​nav_fx:​projectopts_performance.jpg?​direct|}} {{artikel:​nav_fx:​projectopts_performance.jpg?​direct|}}
  
-=== Save project ===+==== Save project ​====
  
 You end up with an overview in the main screen: You end up with an overview in the main screen:
Line 65: Line 69:
 Save this setup as "​OMAP5948ZXF_<​RADIOTYPE>​.jflash"​ for later access. Save this setup as "​OMAP5948ZXF_<​RADIOTYPE>​.jflash"​ for later access.
  
-==== Step 4) Download the firmware ====+===== Step 4) Download the firmware ​=====
  
 {{artikel:​nav_fx:​flash-download_entiry-chip.jpg?​direct&​640|}} {{artikel:​nav_fx:​flash-download_entiry-chip.jpg?​direct&​640|}}
Line 73: Line 77:
 {{artikel:​nav_fx:​flash-download_done_256.jpg?​direct&​640|}} {{artikel:​nav_fx:​flash-download_done_256.jpg?​direct&​640|}}
  
-==== Step 5) Store dump into file ====+===== Step 5) Store dump into file =====
  
 Press ''​Ctrl-S''​ to save the downloaded firmware image into a file. Choose "​*.bin"​ as filetype. Press ''​Ctrl-S''​ to save the downloaded firmware image into a file. Choose "​*.bin"​ as filetype.
  • en/artikel/nav_common/jtag_readout_mainboard_flash.1549634095.txt.gz
  • Last modified: Fri. 08.02.2019 13:54
  • by go4it