-
-
- ]]>
-
- Target status shows that status of the connected target.
-
Current target - selected target configuration.
-
Startup - whether or not the target script ran to completion. Note
- that even if the target is disconnected, powered down or unresponsive, the
- startup script will still run to completion. Startup - OK does not mean
- that the target is fully operational, simply that the configuration script
- did not contain syntax errors for instance.
- See log for details.
-
Target power - Detects power on target.
- If the JTAG cable is not connected, or the target has no power, then no target power will be detected.
-
Type "help power" in telnet for command to control power relay.
- ]]>
-
-
-
-
-
-
-
-
-
- targets.tcl
- documentation.tcl
- Target config quick start guide
-
-
- The reset init script is crucial. It will set up e.g. MMU, chip
- select registers, etc. after a reset. The init.cfg (reset init script)
- is embedded into the openocd.cfg file in the sampls OpenOCD provides.
-
- Writing an openocd.cfg from scratch is a non-trivial exercise, but
- fortunally it only has to be done once for a target and afterwards it
- rarely if ever needs to be changed.
-
-
- ]]>
-
-
- Quick start guide on how to configure a target.
-
-
-
-
-
-
-
-
-
-
- flashinfo.tcl
- Flash
- flashinfo.tcl
- Flash Information
- flashinfo.tcl
-
-
-
-
-
-
-
-
-
-
- Configured flash banks:
-
-
-
- set flash_return [ocd_flash_banks]
- if {[llength $flash_return]!=0} {
- append buffer [encode [flash banks]]
-
- set form_action [formfetch form_action]
- if {[string compare $form_action "Reset CPU and probe flash"]==0} {
- append console [encode [capture_catch "reset init"]]
- append buffer [encode [capture_catch "flash probe 0"]]
- append buffer [encode [capture_catch "flash info 0"]]
- }
- } else {
- append buffer "No flash bank configured."
- }
-
-
-
-
- foreach a [ocd_flash_banks] {
- append buffer "Flash bank at [format "0x%08x size 0x%08x" $a(base) $a(size)]: "
-
-
-
- }
-
-
-
-
- ]]>
-
- Here you will find information about the flash chips that you have
- in your configuration.
-
Reset CPU and probe flash - This will reset the CPU and show
- you more detailed information about your flash. This includes information about
- the different sectors in the flash, and the flash driver used.
- ]]>
-
-
-
-
-
-
- flash.tcl
- flashinfo.tcl
- Program / Verify Flash
-
-
-
- set form_offset [formfetch form_offset]
- set form_action [formfetch form_action]
- set form_type [formfetch form_type]
-
-
- set post ""
- catch {set post $post_data} err
-
- if {[string compare $form_offset ""]==0} {
- set form_offset 0
- }
- if {[string compare $form_type ""]==0} {
- set form_type ""
- }
-
-
-
- set data ""
- append buffer {
-
-
- append buffer {
-
-
- Program and/or verify the flash on your target.
-
Flash - Halt CPU, automatically erase flash if required and program flash with image.
-
Flash and verify - Programs the flash and verifies the programmed flash content is correct.
-
Verify - Halt CPU and verify image in flash or RAM.
-
Offset - This value is added to the address of the image.
- Binary images start at address 0 by default, whereas elf and ihex have addresses encoded into the image.
- Typically 0 for elf/ihex and the address to write the image to for binary files.
- ]]>
-
-
-
-
-
-
-
-
-
-
-
- production.tcl
- flashinfo.tcl
- Production
-
-
- set form_action [formfetch form_action]
- set form_serialnumber [formfetch form_serialnumber]
- append buffer [production_info]
-
-
-
-
- ]]>
-
-
- Upload firmware - Power cycle target, reset target and program raw binary file to flash bank 0, offset 0 and verify flash programming. Leave target powered on.
-
Test - Power up target, run 10 second target test. Output is provided via the DCC output channel.
-
Power on - Power on target.
-
Power off - Power off target.
-
Serial number - A target script can use this string in the production procedure. Type "help production" for more info.
To download log you can also use commands like "wget http://append buffer [ip]/ram/log", or
- point your web browser to said address.
-
- You can also execute tcl commands using curl from your developer PC:
-
-
- curl --form form_command=ocd_version append buffer [ip]runtcl.tcl
-
-
- ]]>
-
-
-
-
-
-
-
- guiupload.tcl
- openocd.tcl
- Upload File
-
-
- set form_filename [formfetch form_filename];
- set form_action [formfetch form_action];
- #set form_filecontent [formfetch form_filecontent];
-
- append buffer {}
-
-
-
- ]]>
-
-
-
-
-
-
-
- targets.tcl
- documentation.tcl
- Target config quick start guide
-
-
- The reset init script is crucial. It will set up e.g. MMU, chip
- select registers, etc. after a reset. The init.cfg (reset init script)
- is embedded into the openocd.cfg file in the sampls OpenOCD provides.
-
- Writing an openocd.cfg from scratch is a non-trivial exercise, but
- fortunally it only has to be done once for a target and afterwards it
- rarely if ever needs to be changed.
-
-
- ]]>
-
-
- Quick start guide on how to configure a target.
-
-
-
-
-
-
-
-
-
-
-
- index.tcl
- index.tcl
- terminal.tcl
- UART forwarding
-
-
- set form_baudrate [formfetch form_baudrate]
- if {[string length $form_baudrate]==0} {
- set form_baudrate [ocd_uart]
- set form_baudrate [string range $form_baudrate 0 [expr [string length $form_baudrate]-2]]
- }
- set form_action [formfetch form_action]
-
-
-
- if {[string compare $form_action "Set baudrate"]==0} {
- append console [encode [ocd_uart $form_baudrate]]
- }
-
-
-
Simple UART
- This terminal window is purely for illustrative purposes. Use telnet or a terminal program
- to talk to the target over TCP/IP for anything but trivial case of reading/writing a few
- lines of texts in simple tests.
-
- ]]>
-
- telnet append buffer [ip] 5555
- or connect via TCP/IP from e.g. HyperTerminal.
-
- Type "help uart" in telnet for information on how to set uart speed for target. Normally
- the uart speed is set from the target configuration script by adding an "uart N", where
- N is the baudrate.
- ]]>
-
+
+
+ ]]>
+
+ Target status shows that status of the connected target.
+
Current target - selected target configuration.
+
Startup - whether or not the target script ran to completion. Note
+ that even if the target is disconnected, powered down or unresponsive, the
+ startup script will still run to completion. Startup - OK does not mean
+ that the target is fully operational, simply that the configuration script
+ did not contain syntax errors for instance.
+ See log for details.
+
Target power - Detects power on target.
+ If the JTAG cable is not connected, or the target has no power, then no target power will be detected.
+
Type "help power" in telnet for command to control power relay.
+ ]]>
+
+
+
+
+
+
+
+
+
+ targets.tcl
+ documentation.tcl
+ Target config quick start guide
+
+
+ The reset init script is crucial. It will set up e.g. MMU, chip
+ select registers, etc. after a reset. The init.cfg (reset init script)
+ is embedded into the openocd.cfg file in the sampls OpenOCD provides.
+
+ Writing an openocd.cfg from scratch is a non-trivial exercise, but
+ fortunally it only has to be done once for a target and afterwards it
+ rarely if ever needs to be changed.
+
+
+ ]]>
+
+
+ Quick start guide on how to configure a target.
+
+
+
+
+
+
+
+
+
+
+ flashinfo.tcl
+ Flash
+ flashinfo.tcl
+ Flash Information
+ flashinfo.tcl
+
+
+
+
+
+
+
+
+
+
+ Configured flash banks:
+
+
+
+ set flash_return [ocd_flash_banks]
+ if {[llength $flash_return]!=0} {
+ append buffer [encode [flash banks]]
+
+ set form_action [formfetch form_action]
+ if {[string compare $form_action "Reset CPU and probe flash"]==0} {
+ append console [encode [capture_catch "reset init"]]
+ append buffer [encode [capture_catch "flash probe 0"]]
+ append buffer [encode [capture_catch "flash info 0"]]
+ }
+ } else {
+ append buffer "No flash bank configured."
+ }
+
+
+
+
+ foreach a [ocd_flash_banks] {
+ append buffer "Flash bank at [format "0x%08x size 0x%08x" $a(base) $a(size)]: "
+
+
+
+ }
+
+
+
+
+ ]]>
+
+ Here you will find information about the flash chips that you have
+ in your configuration.
+
Reset CPU and probe flash - This will reset the CPU and show
+ you more detailed information about your flash. This includes information about
+ the different sectors in the flash, and the flash driver used.
+ ]]>
+
+
+
+
+
+
+ flash.tcl
+ flashinfo.tcl
+ Program / Verify Flash
+
+
+
+ set form_offset [formfetch form_offset]
+ set form_action [formfetch form_action]
+ set form_type [formfetch form_type]
+
+
+ set post ""
+ catch {set post $post_data} err
+
+ if {[string compare $form_offset ""]==0} {
+ set form_offset 0
+ }
+ if {[string compare $form_type ""]==0} {
+ set form_type ""
+ }
+
+
+
+ set data ""
+ append buffer {
+
+
+ append buffer {
+
+
+ Program and/or verify the flash on your target.
+
Flash - Halt CPU, automatically erase flash if required and program flash with image.
+
Flash and verify - Programs the flash and verifies the programmed flash content is correct.
+
Verify - Halt CPU and verify image in flash or RAM.
+
Offset - This value is added to the address of the image.
+ Binary images start at address 0 by default, whereas elf and ihex have addresses encoded into the image.
+ Typically 0 for elf/ihex and the address to write the image to for binary files.
+ ]]>
+
+
+
+
+
+
+
+
+
+
+
+ production.tcl
+ flashinfo.tcl
+ Production
+
+
+ set form_action [formfetch form_action]
+ set form_serialnumber [formfetch form_serialnumber]
+ append buffer [production_info]
+
+
+
+
+ ]]>
+
+
+ Upload firmware - Power cycle target, reset target and program raw binary file to flash bank 0, offset 0 and verify flash programming. Leave target powered on.
+
Test - Power up target, run 10 second target test. Output is provided via the DCC output channel.
+
Power on - Power on target.
+
Power off - Power off target.
+
Serial number - A target script can use this string in the production procedure. Type "help production" for more info.
To download log you can also use commands like "wget http://append buffer [ip]/ram/log", or
+ point your web browser to said address.
+
+ You can also execute tcl commands using curl from your developer PC:
+
+
+ curl --form form_command=ocd_version append buffer [ip]runtcl.tcl
+
+
+ ]]>
+
+
+
+
+
+
+
+ guiupload.tcl
+ openocd.tcl
+ Upload File
+
+
+ set form_filename [formfetch form_filename];
+ set form_action [formfetch form_action];
+ #set form_filecontent [formfetch form_filecontent];
+
+ append buffer {}
+
+
+
+ ]]>
+
+
+
+
+
+
+
+ targets.tcl
+ documentation.tcl
+ Target config quick start guide
+
+
+ The reset init script is crucial. It will set up e.g. MMU, chip
+ select registers, etc. after a reset. The init.cfg (reset init script)
+ is embedded into the openocd.cfg file in the sampls OpenOCD provides.
+
+ Writing an openocd.cfg from scratch is a non-trivial exercise, but
+ fortunally it only has to be done once for a target and afterwards it
+ rarely if ever needs to be changed.
+
+
+ ]]>
+
+
+ Quick start guide on how to configure a target.
+
+
+
+
+
+
+
+
+
+
+
+ index.tcl
+ index.tcl
+ terminal.tcl
+ UART forwarding
+
+
+ set form_baudrate [formfetch form_baudrate]
+ if {[string length $form_baudrate]==0} {
+ set form_baudrate [ocd_uart]
+ set form_baudrate [string range $form_baudrate 0 [expr [string length $form_baudrate]-2]]
+ }
+ set form_action [formfetch form_action]
+
+
+
+ if {[string compare $form_action "Set baudrate"]==0} {
+ append console [encode [ocd_uart $form_baudrate]]
+ }
+
+
+
Simple UART
+ This terminal window is purely for illustrative purposes. Use telnet or a terminal program
+ to talk to the target over TCP/IP for anything but trivial case of reading/writing a few
+ lines of texts in simple tests.
+
+ ]]>
+
+ telnet append buffer [ip] 5555
+ or connect via TCP/IP from e.g. HyperTerminal.
+
+ Type "help uart" in telnet for information on how to set uart speed for target. Normally
+ the uart speed is set from the target configuration script by adding an "uart N", where
+ N is the baudrate.
+ ]]>
+
+
+
+
+
+
+
+
+
\ No newline at end of file
--
cgit v1.2.3