Update 2024-03-27: Greatly expanded the "Samples" page and renamed it to "Glossary".
Update 2024-04-04: Added 5 million mid-2011 posts from the k47 post dump. Browse (mostly) them here.
Update 2024-04-07: Added ~400 October 2003 posts from 4chan.net. Browse them here.

Welcome to Oldfriend Archive, the official 4chan archive of the NSA. Hosting ~170M text-only 2003-2014 4chan posts (mostly 2006-2008).

Threads by latest replies - Page 17

[1373776560] Monitor problem

No.25338 View ViewReplyOriginalReport
I'm a bit new to the whole computer fixing thing so I need a bit of help. My mom just got a new monitor because she was having trouble with the old one. Naturally, I wanted to figure out what was wrong and possibly fix it instead of throwing it out. So I hooked it up and found that from time to time it gives off blurry/smeary lines horizontally across the entire screen. So I have a few questions: 1) what is the problem? 2) is it fixable and how? 3) if I can't fix it, is there anything I can do with it or should I just throw it out?  Thanks

[1371153093] Which linux

No.25235 View ViewReplyOriginalReport
I just bought a new 1 Terabyte external hard-drive, and since I don't really feel like buying the new Windows, I'm thinking of getting... LINUX. I'm fairly new to it, I've run Virtual Machine with Ubuntu and it was pretty great, but I don't know which distro to install into the drive to boot my comp up with.

Recommendations?
13 posts omitted

[1369863585] Tape Backups

No.25212 View ViewReplyOriginalReport
What do you think of tape backups?

[1373505556] Installing SSD with OS

No.25323 View ViewReplyOriginalReport
Hi guys.
I have an SSD that I installed Windows 7 on. I installed it on my current laptop. Can I take the SSD and then put it in my planned Gaming Rig? I'm gonna be using an AMD processor and multiple other components, it it possible - will it still boot up no problem?

Thanks for replies, I really don't know and Google is no help.

[1373229037] How do I install an assembler?

No.25315 View ViewReplyOriginalReport
I've been interested in learning Assembly for over a year now. However, I've made zero progress because I can find any assembler that will work properly. The same thing happens every single time I download a new one: I'll click on the .exe to run it, it'll show command prompt for a split second, and then it'll close.

This doesn't happen for anything else. Only these. Why does it do this, and how do I get it to stop?

[1372421645] How can i raid a chan with kusaba x ?

No.25276 View ViewReplyOriginalReport
SAL

[1369505987] what happened?

No.25201 View ViewReplyOriginalReport
from ddany395

ddany395(01:37:58 (UTC)):alt ffffffhttp://B00BS.INFO?6klys 05w099t8i9qtzewtm

i also have another 3 mails like this.

what do they mean?

[1372401972] Chrome won't delete my fucking forms

No.25275 View ViewReplyOriginalReport
I deleted everything. I cleared my history, my cookies, my cache, my fucking passwords, I checked every fucking box and it still shovess every goddamn typo I ever put into a form back into my face every time I click it. Thread subjects from two fucking years ago keep popping up whenever I click the Subject line, torrents I don't even want to remebmer come back when I click a search bar.

This is fucking bullshit.

[1372830813] Microprocessor System Design

No.25285 View ViewReplyOriginalReport
No. 1: In-Circuit Emulation Exercise

1. OBJECTIVES

1.1 To familiarize with typical in-circuit emulation features.

1.2 Develop necessary skills to design, develop and test a 68000-based microcomputer system with the help of the PC-based MICE-III emulator.

2. LABORATORY

Computer Laboratory

3. EQUIPMENT

Description                              Quantity

IBM Compatible PC                           2
MICE III In-Circuit Emulator System         1
MEX68KECB Educational Computer Board        1
HP54645A Digital Storage Oscilloscope (DSO) 1
Power Supply Unit                           1
MV68K Emulator System Driver Software       1
Multi-meter                                 1
Kermit Communication Software               1

4. INTRODUCTION

An in-circuit emulator (ICE) is a hardware device used to debug the software of an embedded system or system under development as they usually lack keyboards, screens, and other helpful user interfaces.

The basic idea of an "in-circuit emulator" is that it provides an interface into the embedded system. The programmer uses the emulator to load programs into the embedded system, run them, step through them slowly, and see and change the data used by the system's software. ICE's are always tools that attach a terminal or PC to the embedded system. The terminal or PC provides an interactive user interface for the programmer to investigate and control the embedded system.

The term "emulator" is so named as its function is to "emulate" the central processing unit of the embedded system's computer. Often, it literally has a plug that plugs into the same socket as the CPU chip. Emulating the main computer lets it do anything that the main computer can do, but under the control of a programmer.

ICE is an indispensable tool for embedded system development. Without an ICE, the development of embedded systems can be extremely difficult, because there is usually no way to tell what went wrong. With an ICE, the programmer can usually test pieces of code, then isolate the fault to a particular failing piece of code, and then inspect the failing code and rewrite it to solve the problem.

Most ICEs consist of an adaptor unit that sits between the ICE host computer and the system to be tested. A header and cable assembly connects the adaptor to a socket where the actual CPU or microcontroller mounts within the embedded system. Recent ICEs enable a programmer to access the On-chip debug circuit which is integrated into CPU via JTAG in order to debug the software of an embedded systems.

The ICE emulates the CPU. From the system's point of view, it has a real processor fitted. From the programmer's point of view, the system under test is under full control, allowing the developer to load, debug and test code directly. Hence ICE provides the ability to integrate hardware and software development during all phases of the development cycle. The software designer should thus be able to work with the prototype hardware to verify the code to reduce the development time. In addition, the hardware engineer is able to construct the necessary hardware modules and test for conectness with simple test routines, thereby facilitating rapid debug process as the hardware modules are being developed.

The 68000 Educational Computer Board as the target system. A target system is a system under development. Normally, this will include the prototype on a breadboard, wire-wrapping board, or a PCB. The experiment is divided into two sections. The first section focuses on using the emulator to verify and debug on the hardware design. In section two, are steps to debug software by executing it in real-time.

5. EXPERIMENT

In this session you will learn to use the "MICE-III In-Circuit Emulator". Please pay attention to all the features provided on the MICE-III, as you will be heavily relying on the MICE-III to debug and verify most of the hardware and software modules developed by you during subsequent laboratory sessions.

The following tutorial has been prepared to assist you with this hands-on session. Please go through the tutorial below carefully and pay attention to the mini exercises stated there in.

5.1 MICE-III IN-CIRCUIT EMULATOR

5.1.1 Setup

The Motorola Education Computer Board (ECB) is hooked up as the target system, the microprocessor-based system we assume that you wish to test. Verify that the 68000 microprocessor chip of the ECB is removed from it's socket and replaced with the emulator's probe tip connecting the pod cable. Also, the emulator is connected to the PC's RS232-C serial communication port one via the computer port.

5.1.2 Normal Startup

Power up the ECB first followed by Emulator and then the PC. The system configuration is shown in Fig 1.1.



Host PC 1                        Power Supply                            PC 2
                                      |
              Via Computer Port                               Via port 1
             ___________________  Emulator            68000  ____________  Type
                                  MICE III             ECB                KERMIT
Double click
MICE III

Figure 1.1: System Configuration.

Emulator software (mv68k.exe) is provided for the host PC to communicate with the emulator. It resides in the sub-directory c: \mv68k. Follow the steps given below to
execute this driver software.

I. Double click the MICE-III icon made available on the WIN-95 screen

II. The emulator software will perform a self-test. Once this is over, the prompt '>' will appear. This will be referred to as the MICE-III command prompt from now onwards.

III. Should there be any errors, check to ensure that the power supply is switched on and connected to the ECB. Then, exit from the emulator software by entering the command 'ctrl-c' and re-start mv68k once again.

5.2 HARDWARE DEBUGGING

An emulator can be used to verify that "your" hardware design is error-free. The software engineer's model of the hardware design is reflected through the memory map of the system, e.g. Table 1.1 for the case of ECB.

A memory map is a table that shows the range of addresses that are made available to the programmer as memory and memory mapped I/O spaces. Only the proper bus connections and address decoding will result in the memory map as expected.

The emulator provides a feature to allocate memory area within the target system's memory map so that certain operations could be carried out during debugging. This process is termed as overlaying. Hence the term overlay memory. Once defined, the MICE-III will use the overlay memory whenever the CPU performs an access to this memory space. Note that the CPU is unaware of this as the MICE-III is capable of performing the necessary switching in real-time. We will demonstrate a use for this later when S/W debugging is carried out.

To clear any overlay memory (i.e. to map all the memory to the target system), enter
>MAP All E    // The 'E' here means external memory

To verify it is mapped correctly, enter
>MAP
To configure that the DTACK* signal is generated externally, enter
>READY E

5.2.1 TESTING THE TARGET SYSTEM'S (ECB 'S) MEMORY

At any stage, you may press the 'ESC' key to exit to MICE-III prompt

5.2.1.1 System Memory

To display a block of memory block, enter
>MEMORY 0 20 (displays memory from location 0 to location 32)
[Note that the default base system for all numbers is hexadecimal. So, the 20 above is $20 = 32]

5.2.1.2 System Scratchpad Memory

To examine memory contents, enter the following:
>MEMORY 400   (displays 256 bytes ofmemory at a time)


FUNCTION                              ADDRESS

           Exception   ROM/EPROM   $000000-$000007 (1)
           vector      RAM         $000008-$0003FF
           Table

System     Tutor       RAM         $000400-$0008FF
Memory     Scratchpad

User Memory            RAM         $000900-$007FFF

Tutor Firmware         ROM/EPROM   $008000-$00BFFF (1)

Not used                           $00C000-$00FFFF

                     PI/T
               (Lower byte only)   $010000-$01003F

I/O Devices   ACIA2 (Lower byte)   $010040-$010043
              & ACIA1 (Upper byte)     ¦
              Redundant Mapping        ↓
                                    $01FFFF


Not Used                           $020000-$02FFFF

M6800 Page (E6)                    $030000-$03FFFF

Not Used                           $040000-$FFFFFF


Note: (1) Denotes read only


Figure 1.2: ASCII Character Set.
6 posts omitted