Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - CreepNT

Pages: [1]
« on: January 07, 2021, 06:31:49 PM »
Yes, you read this right. The one and only OFFICIAL PLAYSTATION VITA SOURCE DEVELOPMENT KIT, avaliable right at your door.
Made avaliable by yours truly, the Rudy Softwares company. Due to legal reasons, we cannot host the files on this server : you can however order a physical copy.

Attached is a picture of a satisfied customer, showcasing the quality of the RudySDK.

Rudy Softwares
Our passion : Lua retardness your satisfaction ?

PS Vita / [Release] BootMenu
« on: September 20, 2020, 07:05:25 PM »
BootMenu is a GRUB-like menu allowing to automatically bootstrap any baremetal payload and, in turn, Linux, right after the PSVita boots. Recommended for Ensō users only.

VitaLinux build instructions here

Install instructions :

Download BootMenu.skprx from here, and place it on your memory card (i.e. ux0:linux/BootMenu.skprx) or your internal storage (i.e. ur0:tai/BootMenu.skprx).

Then add it to your taiHEN config.txt, in the *KERNEL section, i.e.
Code: [Select]
#For internal memory

#For memory card

Place the baremetal payload at ux0:linux/payload.bin.
Place the Linux zImage and dtb at the location the baremetal payload expects.

Optional :
Can load a background image located at ur0:tai/BootMenu.bmp. Create it with Paint, save as 24bit BMP.

Usage instructions :

For PSVita users :
Use D-Pad Up and D-Pad Down to navigate the menu, O or X to choose an option.

For PSTV users :
Press POWER to abort the countdown and boot the PSVita OS.
Note that the POWER functionality hasn't been tested yet, so it might actually not work  :-\ . I would recommend placing the plugin on the memory card in case it doesn't work. If you can, hop by the Discord and tell me how it works on PSTV.

You can also skip the plugin entierly by holding Triangle/POWER for a bit, after the PS logo appears.

Credits :

teakhanirons : Menu code from EmergencyMount + dev help
xerpi : Linux port for Vita + Vita-baremetal-loader code
Several members of Team CBPS
VitaSDK and DolceSDK maintainers

Changelog :

Version 0.2 : (13/10/2020)
 - Merged the vita-baremetal-loader inside of BootMenu, removing the dependency on an external plugin
   Thanks to xerpi for letting me reuse the code.

Version 0.1 : (20/09/2020)
Initial release[/code]

dev / i can't write a hello world help :megucry:
« on: May 28, 2020, 02:19:57 PM »
 i can't write a hello world help :megucry:

dev / Definite proof the SKGleba bricks Vitas !
« on: May 18, 2020, 07:00:12 PM »
Bricks. An inevitable part of any homebrew scene. Believe it or not but many devs brick their hardware!

Quote from: ImAnEnduser45
so you're telling me i cant trust anybody ?
I'm telling you that there is always a risk involved, and that if you don't want to brick your Vita, don't run homebrew on it.

But as you can see in the following images, the count of PS Vita™️ systems SKGleba has bricked is superior
to the number of stability updates Sony shipped for the Vita (and the Vita is a VERY VERY VERY stable console !!!!!!!)

But he's not alone ! In the journey of coldboot hack for all, @theflow0 bricked a unit trying to downgrade it.

During the Ensō closed test, two unfortunate users saw their Vita die for the community.

The 1.0 version of Ensō suffered from a bug which could led to a brick when uninstalling. This yet again killed a few consoles in the wild.

CelesteBlue made an estimation of the count of boards that died for the sake of the Vitascene or just meming around.
A minute of silence for these poor Vitas that will never come back to life.

please not this may or may not be accurate and CBPS nor myself cannot be held responsible in case it isn't.

Spoiler for those who thinked I was gonna talk shit about SKGleba:
You're stupid.

After teakhanirons told me some guy got VitaSDK to work in WSL (which I already knew since WSL is more or less a Linux VM), I decided to also get Visual Studio Code to work with it. Fortunately, Microsoft released all the tools required to make this a fairly simple process !

Note : I got this configuration working after following dots' tutorial and manually fixing stuff.
This may not be and most likely isn't the best way to configure VSC to do this job, but It Just Works(TM).


Requirements :

For this tutorial, I will use the Debian WSL distribution since it's the one I always install.

Installing the WSL and the VitaSDK/DolceSDK :

Just follow the instructions on MS' website. If you're not familiar with Linux, install Debian as the distribution. Else, choice is up to you.
Don't forget to initialize your distro. Choose whatever you want as the UNIX username and a UNIX password you won't forget (Note that the UNIX password isn't shown when typing it, for security reasons).

Once the distro is ready, install the VitaSDK / DolceSDK following the Linux instructions. For the exports, if you don't know how to edit the .bashrc file, type
Code: [Select]
nano ~/.bashrcThis will open a text editor. Paste the export information at the end of this file, then restart the WSL distro.

Setting up Visual Studio Code :

Install VS Code for Windows then open it.
Click on the Extensions button on the left sidebar, search for C/C++ and Remote - WSL, all made by Microsoft (as shown underlined), and install them.

After both extensions are installed, it is time to configure everything.
Press CTRL+SHIFT+P to open the Command Palette and type Settings json, and look for Open Settings (JSON).

Add the following to your settings.json:
Code: [Select]
    "cmake.buildDirectory": "${workspaceRoot}/build/${buildType}",
    "cmake.configureOnOpen": true,
    "cmake.cmakePath": "/usr/bin/cmake",
    "cmake.generator": "Unix Makefiles"

Be sure to have a proper syntax.
Here's what settings.json could look like (I also disabled the telemetry and changed a few other settings, which is optional) :
Spoiler for settings.json:

Now, go into your WSL terminal, and browse to a project's directory, then type
Code: [Select]
code .
This should install the Visual Studio Code server for WSL, and open a new VSC window.
Go back to the Extensions panel. You should now have two panel : Local and WSL - Debian (or whatever distro you chose), with the latter empty.
Click on the Install in WSL: <distro> button of the C/C++ extension. Search for CMake and install the CMake Tools extension (NOT CMake !) by Microsoft.

Open the Command Palette again, and type cmake, and look for Edit User-Local CMake Kits. You might get a message saying you don't have any kits, click on Accept of whatever the button is. This should then open cmake-tools-kits.json.
Add the following at the beggining, just after the opening bracket ( [ ) :
Spoiler for VitaSDK users:
Code: [Select]
    "name": "VitaSDK",
    "toolchainFile": "/usr/local/vitasdk/share/vita.toolchain.cmake",
    "preferredGenerator": {
      "name": "Unix Makefiles"
    "environmentVariables": {
      "VITASDK": "/usr/local/vitasdk",
      "CMT_MINGW_PATH": "/usr/local/vitasdk/bin"
Spoiler for DolceSDK users:
Code: [Select]
    "name": "DolceSDK",
    "toolchainFile": "/home/YOURUSERNAME/.local/dolcesdk/share/dolce.toolchain.cmake",
    "preferredGenerator": {
      "name": "Unix Makefiles"
    "environmentVariables": {
      "DOLCESDK": "/home/YOURUSERNAME/.local/dolcesdk",
      "CMT_MINGW_PATH": "/home/YOURUSERNAME/.local/dolcesdk/bin"

Example cmake-tools-kits.json (not the full file) :
Spoiler for cmake-tools-kits.json:

Make sure you saved all the config files. CMake should now be configured.
Look at the bottom left corner of the Window, you should see "No Kits Selected", click on that and change it to "VitaSDK"/"DolceSDK".

You should be able to build now by clicking the "Build:" button in the same bottom bar area, or pressing F7.

Quote from: dots_tb
If it doesn't work the first time:
  • Navigate to the location of the source folder and look inside it.
  • Make sure there is no build folder.
  • Open the command palette and then type Developer Reload and reload the window
And with luck, it should configure CMake and allow you to build the project.

Setting up Projects :

You will have to do this for every new project !
Reminder : to open a new project, open its folder in the WSL terminal and type code .

Open the Command Palette and type C++, then look for C/C++: Edit Configurations (UI)

Add a new configuration called VitaSDK/DolceSDK and set the compiler path to :
Spoiler for VitaSDK users:
Code: [Select]
Spoiler for DolceSDK users:
Code: [Select]

Scroll down and un-collapse Advanced Settings then look for and set the Browse Path to the following:
Spoiler for VitaSDK users:
Code: [Select]
Spoiler for DolceSDK users:
Code: [Select]

This should set up IntelliSense.
Note : You might have to select the VitaSDK/DolceSDK configuration in the bottom right corner of the window.

With that, you should now be able to enjoy VS Code for your PS Vita software development.

Note: In case you want to make a new project and VSC doesn't connect to the WSL automatically, open the Command Palette, type WSL and click
on Remote-WSL : New Window

Optional : Enabling WSL2

WSL2 is a not-yet-finished update to the WSL. While WSL1 is more like a compatibility layer, WSL2 runs a containerized Linux kernel, hence being more of a VM than WSL1 was. To enable WSL2, see here.

Pages: [1]