gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS development > Fixed

#72753 - Mollusk - Tue Feb 21, 2006 11:50 am

I just noticed a strange bug when running some code from the MK3 : the X and Y buttons take like 2 seconds to update (either going on or off).
Has anyone noticed this before ?? My code works perfectly well if I flash the rom directly on a EZFlash or Neoflash cart, and works on Supercard...


Any ideas ?

Edit : just noticed that my stylus updates every 2 seconds two...

Edit 2 : changed 2 bits of code around in the IRQ init and it worked, not sure why... but at least it works, lol
_________________
PAlib official forum : http://www.palib.info
PAlib official tutorials: http://www.palib.info/wiki
Updates, help, code examples, tutorials, etc...

#73727 - Payk - Mon Feb 27, 2006 9:10 pm

haha there are many strange things like that. at our project mousearrow jumps on my hardware at releasing stylus...but on other devices not...hope that its not because of a touchscreen error...hehe no on my sisters ds is same thing so its a sc sd thing i think... perhaps just with my inputcode... But why all flashcards ahve different bugs? i mean they dont patch rom, and they just copy that arm codes to cpu ?!?!?!

#73734 - Mollusk - Mon Feb 27, 2006 10:49 pm

the bug reappeared today, not sure why :s It works on EZFlash but not on MK3
_________________
PAlib official forum : http://www.palib.info
PAlib official tutorials: http://www.palib.info/wiki
Updates, help, code examples, tutorials, etc...

#73743 - cory1492 - Mon Feb 27, 2006 11:45 pm

Payk - because they all deal with memory clearing differently when launching homebrew, and there are likely remnants in the memory from the menus they use after launching that could cause problems. Make sure you are initializing the hardware too just in case that helps, something like "POWER_CR = POWER_ALL_2D;" (note that this swaps screens as a side effect) or similar.

Mollusk: I suspect the MK2/3 menu is the culprit, not certain but I suspect that the ARM7 isnt getting handed off to the code correctly (or is perhaps substituted entirely in the case of homebrew) - which menu version are you using to load the homebrew? Some versions did not handle the touch code very well, but I think that was fixed in menu 0.5.

#73847 - Mollusk - Tue Feb 28, 2006 9:54 am

I was trying versions .4 and .5, same thing... (.4 seems weird because everything starts blinking in the menu when I have too many files on my SD :S)
_________________
PAlib official forum : http://www.palib.info
PAlib official tutorials: http://www.palib.info/wiki
Updates, help, code examples, tutorials, etc...

#73848 - Payk - Tue Feb 28, 2006 10:12 am

hmhm makes sences...... how could a programm dels itselfs out of ram... heehe ok NICE interesting... i am going to clear all arrays after init.