Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • minipax
    Participant
    Post count: 4

    I’ve done some experimenting with the values in config.txt.

    The default values for Rpi2 overclock is

    arm_freq=1000
    core_freq=500
    sdram_freq=500
    over_voltage=2

    I tested by commenting out one by one, and the only setting that effects the CB is core_freq. At 500 there is no reaction from the controllers, at 275 it’s total mayhem (scrolling, clicking etc by it self), and at 265 it’s usable but doesn’t register all input, some double clicking etc. At 260 it seems stable with no ghosting, so now I’m running with these values:

    arm_freq=1000
    core_freq=260
    sdram_freq=500
    over_voltage=2

    Any good explanation to why the core_freq has such an impact on the CB’s behavior?

    minipax
    Participant
    Post count: 4

    I’m using two NES controllers via CB, and planning to use two usb SNES and two wired xbox 360’s depending on what emulator I’m using (and maybe some usb N64 in the future).

    Currently I’m looking into this post to make the mess work, if it’s even possible.

    edit: short answer is yes, as long as you don’t mind figuring out which controller is where etc.

Viewing 2 posts - 1 through 2 (of 2 total)