DieselDummy's CSO build - #1

[DieselDummy]

Thought I'd share my first build. It's a Circuit Sword build from the first round of orders, so there's not much that hasn't been seen.

Black shell, clear blue buttons, two PSP1000 joysticks, my personal "BatteryCoverButtons" for shoulders/triggers, YaYas screen glass and optimization. HoolyHoos stormtrooper theme.

I did, however, overclock the cm3 pretty high and have DiddyKong Racing running flawlessly.

The game cartridge is a clear blue and I added a couple blue LEDs to illuminate with power on.

Also, made the holes for the CSO LEDs in front instead of on top. That placement seems to have adjusted the brightness to a more comfortable level for my taste.

[Hellweaver666]

Looks sweet - illuminated case modding seems to becoming a thing in the GBZ community this week.

Great job though, looks clean!

I'm interested to know, looking back. Is there anything you would have done differently?

[RxBrad]

I won't lie. That glowing cartridge looks cool as all heck.

[DieselDummy]

I'm interested to know, looking back. Is there anything you would have done differently?

Only thing I would've done differently is make the time to finish this build sooner! I did have some unforseen circumstances, however, (newborn not sleeping for months) but that was out of my hands.
Kite did an amazing job with simplifying this build process and simultaneously maximizing it's potential. Amazing to say the least, but I know he doesn't need us to tell him that.

How far did you get the OC to go? it looks really good by the way!

I will have to check the numbers when I get home in order to specify accurately. But, if I remember correctly, I was trying to push it as far as the max for the Pi3B+ and I may have went a little further. Please don't quite me on that yet. I do remember being pleasantly surprised to see no kernel panics or freezing the entire time. I will update with exact OC numbers as soon a I can.

[DieselDummy]

How far did you get the OC to go?

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
total_mem=1024
arm_freq=1550
gpu_freq=500
core_freq=500
sdram_freq=500
sdram_schmoo=02000020
over_voltage=6
sdram_over_voltage=2
v3d_freq=525

thats what i got in my config, however, when i run command

Code: Select all

$ lscpu

the CPU max MHz is 1200,0000

hope that answers the question

[kite]

How far did you get the OC to go?

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
total_mem=1024
arm_freq=1550
gpu_freq=500
core_freq=500
sdram_freq=500
sdram_schmoo=02000020
over_voltage=6
sdram_over_voltage=2
v3d_freq=525

thats what i got in my config, however, when i run command

Code: Select all

$ lscpu

the CPU max MHz is 1200,0000

hope that answers the question

Maximum CPU frequency (e.g. when your CPU is under load)

Code: Select all

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

Minimum CPU frequency (when your CPU is idle)

Code: Select all

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq

Current CPU frequency (it up/down clocks under load):

Code: Select all

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq

Also this in KHz:

Code: Select all

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

ALSO this code tells you for ALL the cores on the Pi3/CM3:

Code: Select all

find /sys/devices/system/cpu/cpu[0-3]/cpufreq/scaling_cur_freq -type f | xargs cat | sort | uniq -c

[DieselDummy]

Screenshot_20181117-084341.png (1.18 MiB) Viewed 11537 times

Cpu max...1200000
Cpu min... 600000
Cur freq... 1200000
Scaling... 600000
All cores... 4 1200000

Why do I feel like I'm not much help?
Was I reading that correctly, you wanted me to run those commands? I'm still very much in a noob when it comes to any kind of programming. But trying to learn. Is this even a significant difference in CPU capability? I have certainly noticed a huge difference in gameplay. Even GoldenEye is almost functioning normally on level 2

[kite]

Well that's good to hear, it's funny that the numbers from those commands don't seem to match up with the settings, so, *shurg* if it works it works

[DieselDummy]

Well that's good to hear, it's funny that the numbers from those commands don't seem to match up with the settings, so, *shurg* if it works it works

I'm curious though, how can I measure under load accurately if I can't play the game and do those commands at the same time? Second question, what should those commands be reading if my config.txt is what I entered? Third question, do you have any recommendations to improve performance? (It is understood that I assume all responsibility for damage to the pi) Final question, could the pi be trying to protect itself somehow, or do my adjustments just make no sense?

[DieselDummy]

Also I wonder if something in YaYas optimization guide is having an effect on this as well....