Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't know (not enough details) but your memory test may be a cache test and might not test any RAM at all.</p> <p>Your memory test (if it does test memory) is also very badly designed. For example, you could chop (or short out) all of the address lines and all data lines except for the least significant 2 data lines, and even though there'd be many extremely serious faults the test will still pass.</p> <p>My advice would be to read something like this web page about memory testing, just to get some ideas and background information: <a href="http://www.esacademy.com/en/library/technical-articles-and-documents/miscellaneous/software-based-memory-testing.html" rel="nofollow">http://www.esacademy.com/en/library/technical-articles-and-documents/miscellaneous/software-based-memory-testing.html</a></p> <p>In general, for non-destructive tests you'd copy whatever you want to keep somewhere else, then do the test, then copy the data back. It's very important that "somewhere else" is tested first (you don't want to copy everything into faulty RAM and then copy it back).</p> <p>I would also recommend using assembly (instead of C) to ensure no unwanted memory accesses are made; including your stack.</p> <p>If your code is in RAM that needs to be tested then you will probably need 2 copies of your RAM testing code. You'd use the second copy of your code when you're testing the RAM that contains the first copy of your code. If your code is in ROM then it's much easier (but you still need to worry about your stack).</p>
    singulars
    1. This table or related slice is empty.
    1. PORAM Checksum in C language
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBrendan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COthe problem is i would still have to check the stack. Could i still control memory access to avoid using asm?
      singulars
      1. PO
      1. USRobertoNovelo
    2. COIf no functions are called, no IRQs are possible and you can guarantee that no local variables are on the stack; then you're not using the stack while testing and can copy the stack somewhere, test the RAM, then copy the stack's data back. Of course the "register" keyword is a deprecated joke (most compilers ignore it) and doing all of this in a single function without too many local variables is nearly impossible.
      singulars
      1. PO
      1. USBrendan
    3. COAn alternative would be to switch to a different stack when you need to test the RAM that the original stack uses; but you can't do that in C either (and if you use minimal pieces of inline assembly for stack switching only, then you have to worry about where the compiler stored arguments and local variables on the original stack). In both cases (not using a stack and using a different stack), attempting to do it in C is "less than sane".
      singulars
      1. PO
      1. USBrendan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload