Working with the 8088 Intel's microprocessor

  • Thread starter Thread starter Rainier9
  • Start date Start date
AI Thread Summary
Working with the 8088 microprocessor presents challenges, particularly for implementing a Graphic Liquid Crystal Display (GLCD) and an RF-ID reader, as it requires handling additional components. Alternatives like the PIC16F877A from Microchip or Arduino are recommended for ease of use. While assembly code for the 8088 is manageable, the project's complexity will significantly influence the difficulty level, especially when real-world conditions and debugging are involved. Writing in C can be as efficient as assembly for many applications, with assembly mainly reserved for specific high-performance needs. Ultimately, the success of the project hinges on the requirements and the ability to interface effectively with the devices.
Rainier9
Messages
32
Reaction score
0
Hi everyone, I was wondering if any of the students or engineers here have ever worked with the 8088 microprocessor?

If so, how difficult (in terms of Assembly code) would be to implement a Graphic Liquid Crystal Display (GLCD) and a RF-ID reader? I have more concern in the glcd than the rf-id reader, since the reader woule just gives hexadecimal data to microp.
 
Engineering news on Phys.org
8088 - Not a friendly chip for what you want to make.

Lots of better choices by Microchip, Atmel and others.

Look at the PIC16F877A. (You'll thank me later.)
 
I can only echo the above. Why would you use an 8088 and have to handle the extra chips when a PIC will do everything in one package.
 
It's because is required for a class. Otherwise I'd just use an Arduino. Thanks for answering though! More opinions are welcome as well.
 
Do you need to actually write in assembly code? You can write your code in C, and it will be just as fast as assembly. The only justification nowadays for writing things in assembly is for special instructions (which you can embed in C anyway) and very high-performance segments.

Having said that, assembly for the x86 is not difficult at all; but, the difficulty of your project will depend on the complexity of what you want to do, to the interface to those devices, and to the transfer methods you want to use.

Also, a big factor is whether you need to actually make these things to work. If you just need to do some basic interfacing routines, that's one thing... but if you need to initialize / monitor / recover these devices, and go after real-world timining and debugging issues... that can get very complicated very easily, because it's one thing to make an exercise for class.. another to make the darn think to work in real-world conditions.
 
Thread 'Weird near-field phenomenon I get in my EM simulation'
I recently made a basic simulation of wire antennas and I am not sure if the near field in my simulation is modeled correctly. One of the things that worry me is the fact that sometimes I see in my simulation "movements" in the near field that seems to be faster than the speed of wave propagation I defined (the speed of light in the simulation). Specifically I see "nodes" of low amplitude in the E field that are quickly "emitted" from the antenna and then slow down as they approach the far...
Very basic question. Consider a 3-terminal device with terminals say A,B,C. Kirchhoff Current Law (KCL) and Kirchhoff Voltage Law (KVL) establish two relationships between the 3 currents entering the terminals and the 3 terminal's voltage pairs respectively. So we have 2 equations in 6 unknowns. To proceed further we need two more (independent) equations in order to solve the circuit the 3-terminal device is connected to (basically one treats such a device as an unbalanced two-port...
Back
Top