Main Menu
Main Page
Forums
Recent changes
Random page
Help

Databases
GlitchDex
AttackDex
ItemDex
TrainerDex
TypeDex
UnownDex
More

Major Glitches
Trainer escape glitch
Old man trick
Celebi Egg trick
Select glitches (Japan)
SRAM glitch
CoolTrainer♀ corruption
LOL glitch
Rival LOL glitch
Super Glitch
ZZAZZ glitch
Pomeg corruption glitch (Glitzer Popping)
Tweaking
Elite Four door glitch (Japan)
Pokémon merge glitch
Pokémon cloning
Time Capsule exploit
Arbitrary code execution
Coin Case glitches
More

Other Glitch Categories
Glitches by generation
Glitches between two generations
Japan-only/language specific glitches
Music glitches
Natural glitches
Non-core series glitches
Non-Pokémon glitches
Officially acknowledged glitches
Recurring glitches
Dead glitches

References
Pokémon GameShark codes
The Big HEX List
Glitch Pokémon cries
GB programming
Curiosities
Debugging features
Easter eggs
Error traps
Glitch areas
Glitch myths
Non-glitch exploits
Placeholder texts
Pokémon glitch terminology
Unused content and prerelease information

Useful Tools
8F Helper
GBz80 to Items
Old man trick name generator
PATH (Prama's Advanced Tweaking Heaven)
Save file editors
Special stat/Pokémon converter
Trainer escape Trainer Pokémon finder

Affiliates
Legendary Star Blob 2 (Hakuda)
Pokémon Speedruns wiki
PRAMA Initiative
Become an affiliate!

Technical
Site Source Code

Search Wiki

 

Search Forums

 

Author Topic: DS/i Video Oddities  (Read 274 times)

0 Members and 1 Guest are viewing this topic.

Yeniaul

  • Guest
DS/i Video Oddities
« on: August 20, 2016, 11:10:50 pm »
I was looking things up on the pre-3D DS family and noticed odd work-arounds in play:
Apparently a VBlank is handled exactly the same way as a GB/C/A, with a few exceptions:
The top screen has the very first blank on startup (top screen blank will be referred to as a TBlank, bottom blank as BBlank) and the updating alternates instead of being processed simultaniously. You can also manipulate VRAM (or equivalent) when disabled, as the data you try to manipulate will be buffered and your manipulations will automatically be applied on the next blank. Each screen has its own section of VRAM, separated by a copy of NAND. There's an odd quirk with processing: The screens have their own processor, the bottom uses the ARM9 and the top uses the ARM7. They time blanks via a segment of code on the NAND. Oh, and one screen is always under a Blank period.

This is formatted REALLY BADLY, but it's 1:08 AM and my DSi can't hold any more characters.