Databases
StackOverflow2013
Usersdbo
USJubatian
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USJubatian
    primarykey
    data
    text
    plurals
    1. POAVR 8bit, C standard compliance regarding bit accessing of SFRs
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. POFinding seeds for a 5 byte PRNG
      singulars
      1. PTQuestion
    1. POFinding seeds for a 5 byte PRNG
      singulars
      1. PTQuestion
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWrapping in macros is the way how it should work I think. The problem with the current approach is inconsistency (like `GIFR |= 1U << 6;` and `var = 6; ... GIFR |= 1U << var;` producing fundamentally different results), not to mention that how I can be sure that through optimization or various layers of indirections the expansion to `SBI` or `CBI` won't fail. So I would except these constructs resolving to R-M-W while having macros for the delicate stuff which have their well-known constraints and can be expected to work reliably.
      singulars
      1. PO
      1. USJubatian
    2. COAn interesting effect which sure is visible if you try to clear interrupt flags (datasheet pg. 70). If you do one like `GIFR |= 1U << 6;` then it will "work" (only the intended flag will clear). However if you attempt to clear two like `GIFR |= (1U << 6) | (1U << 7);`, then all 3 will clear, and bang, you have a bug in there. From C level I would except these two behave similarly (either both clearing all flags due to R-M-W or both clearing only the flags I explicitly specified) however it is clearly not the case here.
      singulars
      1. POAVR 8bit, C standard compliance regarding bit accessing of SFRs
      1. USJubatian
    3. COHe was trying to interface a parallel alphanumeric LCD. We had experience with these from earlier with PIC18s using C, I originally recommended him to just take one of those and port it. The LCD did not work (like if we did not communicate with it at all). Then looking in the problem and skimming through the ported code I concluded this, he did it, and the LCD worked as the code dictated. In the prev. code there were stuff like `PORTC |= (1U << 6) | (1U << 7);` which obviously won't translate to `SBI`, so true R-M-W happens, then see above. Datasheet does not define R from PORTx.
      singulars
      1. POAVR 8bit, C standard compliance regarding bit accessing of SFRs
      1. USJubatian
 

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