[SOLVED] CSO - Mode button for volume not working

[jermzz]

Issue solved please see issue #17 on kite’s Github:

https://github.com/kiteretro/Circuit-Sw ... -367058866

———————————————————/


Hello,

Built my first Circuit Sword gameboy, and it is amazing.

Everything is perfect except the sound.

First issue is that it's not so loud. If i turn ES volume to 12db it is a good volume. Not "loud" by any means, but it's audible enough to hear and be content with.

But if I turn ES volume back down it's pretty low. Low enough to where I wish it was higher. The first time went into volume setting in retropie, it was at 100%. after being in game and trying to use mode + up or down on dpad which did not work, I went back to check the volume and it was at 0. So i turned it up, exit out, immediately go back to the same menu and it's back at zero. Strange because when I go in game, I still have the same volume level, but again I can not change volume at all unless I go into retroarch by pressing select + x and changing it there.

I SSH in and checked alsa, which all the time shows 100% on the onboard audio chip.

For kicks I tried to use the update.sh, but same thing.

I have two different SD cards with Kite's image installed and they both have the same issue. Thanks in advance for any help. I feel it's probably something stupid I haven't done. I accidentally found out through trial and error that mode +y is mute and opposite for x. All other mode functions are working as expected except volume.

thanks!

[kite]

Hi,

As an FYI, the osd script will keep resetting the volume level on change, so setting it in alsamixer will change pretty soon after if the button combo decides to set it. There are definitely some improvements that can be made in this area to make it WAY better and I do plan on addressing it in a few weeks..

Can you let me know the output to the following:

1. SSH in
2. sudo service cs-osd stop
3. miniterm.py /dev/ttyACM0
4. Press the "f" key, each press should show you a number, this is what the arduino is telling the Pi to set it to.
5. Hold MODE + UP/DOWN for a few seconds
6. Press the "f" key again, does the number change?
7. CTRL + ] (to exit)
8. sudo service cs-osd start

Have you done anything like calibrating the joystick or something?

[jermzz]

Hi,

As an FYI, the osd script will keep resetting the volume level on change, so setting it in ES or alsamixer will change pretty soon after if the button combo decides to set it. There are definitly some improvements that can be made in this area to make it WAY better and I do plan on addressing it in a few weeks..

Can you let me know the output to the following:

1. SSH in
2. sudo service cs-osd stop
3. miniterm.py /dev/ttyACM0
4. Press the "f" key, each press should show you a number, this is what the arduino is telling the Pi to set it to.
5. Hold MODE + UP/DOWN for a few seconds
6. Press the "f" key again, does the number change?
7. CTRL + ] (to exit)
8. sudo service cs-osd start

Have you done anything like calibrating the joystick or something?

Kite,

Thanks for the response. When I run the command and press “f” the number that repeats is 255.

It does not matter how many times I press mode + up or down, nor does it matter how long I hold it. It still returns 255 every time. I assume this means it’s not changing the volume.

I have calibrated the joystick. Just the one time as per the wiki and it worked immediately.

Thanks

[kite]

Can you update the arduino code, and also run the ./update.sh (in the Circuit-Sword directory on the Pi). I have pushed some changes that may help!

Reboot once done

[jermzz]

Can you update the arduino code, and also run the ./update.sh (in the Circuit-Sword directory on the Pi). I have pushed some changes that may help!

Reboot once done

Kite,

I have done the update.sh via ssh and rebooted multiple times. I have also updated the Audrino code from what's currently in your repository. I know the update worked, because I fixed my inverted joystick while I was in there and that worked just fine.

Outcome for volume is still the same. The problem persists. Still getting 255 also when it takes the Audrino reading.

help

[kite]

Great job, thanks for this it's really helping understand what the issue is! I have added a new comment to the issue https://github.com/kiteretro/Circuit-Sw ... -366892950 can you please try those steps in my latest comment at the bottom? Basically refresh your code and upload again, then calibrate joystick (even if you have no joystick, this step is important)

EDIT: Issue is now fixed. Follow the link to the issue in github and follow the steps at the end of the posts

[RhinoNigel]

I can’t seem to fix the first image with the steps you’ve given on github and the newest image, I extract it and there’s 3 files, one is an image called “1” and it doesn’t work. Any way to get this image to work or help me with the first one? Thanks!

[kite]

I can’t seem to fix the first image with the steps you’ve given on github and the newest image, I extract it and there’s 3 files, one is an image called “1” and it doesn’t work. Any way to get this image to work or help me with the first one? Thanks!

Sounds like you're doing something very wrong, are you following these steps: https://github.com/kiteretro/Circuit-Sw ... ork-at-all

[RhinoNigel]

Yeah I’m using putty and typing/following these steps exactly:

Enable WiFi
SSH in
cd Circuit-Sword
sudo ./update.sh YES
sudo apt-get install avrdude
sudo ./flash-arduino.sh
sudo reboot
Power off normally. Then HOLD START AND POWER ON (to do a joystick calibration)
Done! Adjust volume as normal.

I can’t seem to fix the first image with the steps you’ve given on github and the newest image, I extract it and there’s 3 files, one is an image called “1” and it doesn’t work. Any way to get this image to work or help me with the first one? Thanks!

Sounds like you're doing something very wrong, are you following these steps: https://github.com/kiteretro/Circuit-Sw ... ork-at-all

[kite]

Screenshot of the error?