Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 11 and Version 12 of TBR/BSP/Mvme147s


Ignore:
Timestamp:
12/08/10 13:30:30 (14 years ago)
Author:
Jgeralnik
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • TBR/BSP/Mvme147s

    v11 v12  
    5757
    5858
    59 There are various ways to enter a user program into system
    60 memory for execution. One way is to create the program using the
    61 Memory Modify (MM) command with the assembler/disassembler
    62 option. You enter the program one source line at a time. After each
    63 source line is entered, it is assembled and the object code loads into
    64 memory. Refer to the MVME147 BUG 147Bug Debugging Package
    65 User's Manual for complete details of the 147Bug Assembler/
    66 Disassembler.
    67 Another way to enter a program is to download an object file from
    68 a host system. The program must be in S-record format (described
    69 in the MVME147BUG 147Bug Debugging Package User's Manual) and
    70 may have been assembled or compiled on the host system.
    71 Alternately, the program may have been previously created using
    72 the 147Bug MM command as outlined above and stored to the host
    73 using the Dump (DU) command. A communication link must exist
    74 between the host system and the MVME147. The file is downloaded
    75 from the host to MVME147 memory by the Load (LO) command.
     59There are various ways to enter a user program into system memory for execution. One way is to create the program using the Memory Modify (MM) command with the assembler/disassembler option. You enter the program one source line at a time. After each source line is entered, it is assembled and the object code loads into memory. Refer to the MVME147 BUG 147Bug Debugging Package User's Manual for complete details of the 147Bug Assembler/Disassembler.
     60Another way to enter a program is to download an object file from a host system. The program must be in S-record format (described in the MVME147BUG 147Bug Debugging Package User's Manual) and may have been assembled or compiled on the host system. Alternately, the program may have been previously created using the 147Bug MM command as outlined above and stored to the host using the Dump (DU)  command. A communication link must exist between the host system and the MVME147. The file is downloaded from the host to MVME147 memory by the Load (LO) command.
     61
    7662= Debugging =
    7763