What is the best way to test the microprocessor until failure

This is a discussion on What is the best way to test the microprocessor until failure within the C Programming forums, part of the General Programming Boards category; Please help me! I need to write the program that tests the microprocessor until it fails. Could anyone please give ...

  1. #1
    Registered User
    Join Date
    Mar 2002
    Posts
    54

    Angry What is the best way to test the microprocessor until failure

    Please help me! I need to write the program that tests the microprocessor until it fails. Could anyone please give me any advice? Thanks!

    I use the Hitachi C compiler
    Last edited by vnrabbit; 03-12-2002 at 01:10 PM.

  2. #2
    B26354 Deckard's Avatar
    Join Date
    Jan 2002
    Posts
    633
    Code:
    while(1) { fork(); }
    No wait, that's memory

    I suggest an endless loop of meaningless mathematical calculations. Anyone else have an idea here?
    Jason Deckard

  3. #3
    Registered User
    Join Date
    Oct 2001
    Posts
    22

    write the program that tests the microprocessor

    hey Vnrabbit,

    what is your compiler, try to mention it at the first time, so that it becomes easy to understand.

    thanx...
    take care...
    ___________

    ART is LONG...
    ___________
    Jackie

  4. #4
    Scourfish
    Guest
    Why not try some recursion?

    int crabgrass(word phillipshead, word flathead)
    {
    crabgrass(phillipshead+1, flathead+1);
    }

    But then again, I'm probably talking out of my ass.

  5. #5
    Registered User
    Join Date
    Mar 2002
    Posts
    54
    Sorry, I use the Hitachi compiler.

  6. #6
    ....
    Join Date
    Aug 2001
    Location
    Groningen (NL)
    Posts
    2,386
    I don't know how to let a microprocessor fail. But isn't there in your documentation something with "you shouldn't do this", "don't do this", "better not try this"?

    What microprocessor are you using, I guess one of the SH-family?
    You try a search with Google on "Hitachi SH problems", or something like that. I think you need to dive deep into the hardware architecture of the microprocessor to understand which things could go wrong.

  7. #7
    Registered User
    Join Date
    Oct 2001
    Posts
    375
    If by test until you detect a failure, then you have a lot of work cut out for you. Circuit test vectors are tedious at best and something a complicated as a processor will require some rather hefty technical documentation. And it will definitely need to be done in assembly so as to know exactly what commands are being used.

    Just to test some of the limited ALU components, you could, for example, come up with a table of calculations and expected results and have the CPU do the calculations, then compare them to see if they were accurate. You are assuming, of course, that a lot of other components aren't at fault with this simulation as well.

    If, on the other hand, you want to write code to physically damage a CPU, then you are out of luck. The CPU clock regulates the CPU. It doesn't matter if it is "busy" or not, it can't "overload". (However, some rather nasty viruses of the past targeted a specific architecture for vulnerabilities in the circuit designs... but that was for a specific mother board or device, and it isn't bloody likely you could find such a vulnerability today - not without investing so much time that the board would be obsolete by the time you finished anyway....)

    Well, I'm going to have to accomplish some work today eventually I suppose.... that was fun though.

    -Justin
    Allegro precompiled Installer for Dev-C++, MSVC, and Borland: http://galileo.spaceports.com/~springs/

  8. #8
    Registered User
    Join Date
    Mar 2002
    Posts
    54
    Thanks for all the answers!
    Like Justin said:
    >>Just to test some of the limited ALU components, you could, for example, come up with a table of calculations and expected results and have the CPU do the calculations, then compare them to see if they were accurate. You are assuming, of course, that a lot of other components aren't at fault with this simulation as well

    That is what I want to do at this point. I need to test the processor for failed operation, bit flips-errors, count and log the errors. In addition the test should run continuously to test. Please give me any idea. Thanks!

  9. #9
    Unregistered
    Guest
    Actually if you can get the CPU into SMM or System Management Mode you can change the clock frequency at will. However, these are CPL 0 instructions and under Windows and most OS's you don't have CPL 0. Also to get into SMM mode you must assert
    pin #21 on the CPU (for Intel, not sure about AMD) which causes
    the CPU to issue an SMM interrupt.

    I have no idea how to actually cause pin 21 to go high and to do this just to cause your CPU to fail, is braindead at best.

  10. #10
    Super Moderator VirtualAce's Avatar
    Join Date
    Aug 2001
    Posts
    9,596
    How am I supposed to get my post count up if I keep forgetting to sign in?

    That was Bubba on the unregistered name.


Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Integer Emulation
    By Elysia in forum C++ Programming
    Replies: 31
    Last Post: 03-18-2008, 01:03 PM
  2. undefined reference
    By 3saul in forum Linux Programming
    Replies: 12
    Last Post: 08-23-2006, 05:28 PM
  3. C++ Operator Overloading help
    By Bartosz in forum C++ Programming
    Replies: 2
    Last Post: 08-17-2005, 12:55 PM
  4. MSVC Template Constructor/Assignment Errors
    By LuckY in forum Windows Programming
    Replies: 3
    Last Post: 07-22-2005, 02:57 PM
  5. Question About Linker Errors In Dev-C++
    By ShadowMetis in forum C++ Programming
    Replies: 9
    Last Post: 08-18-2004, 08:42 PM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21