Live data from Hacker News

SNES Development Part 1: Getting Started

blog.wesleyac.com

41–48 of 48 posts

Re: SNES Development Part 1: Getting Started

#41
post #18

Personally instead of Mesen-S, I'd use the fork at https://github.com/NovaSquirrel/Mesen-SX , which contains a fix for saving settings on Linux Mono 6.12 ( https://github.com/NovaSquirrel/Mesen-SX/commit/c374ca8b9ed3... ). I'm more interested in SPC700 development for SNES music. Mesen-SX has a SPC debugger separate from the main debugger, but I'm not sure if it's more or less useful than bsnes-plus (I know the Mesen…

A friend of mine from high school is working on a SNES tracker[0]. He’s deep into this space and could probably answer your questions if you catch him on stream[1]. He also authored many of the sections on the SNES development wiki linked by the article (under “bazz”). [0] https://github.com/bazz1tv/snestracker [1] https://www.twitch.tv/Bazz1tv

is this the legendary M Bazzinoti?

Re: SNES Development Part 1: Getting Started

#42
post #7

also check out the bass asembler https://github.com/ARM9/bass and the snes dev kit https://github.com/alekmaul/pvsneslib

I generally advise against using bass for home-brew development. Bass is not a very well thought out assembler. I've never used it for 65816, but for other architectures like MIPS has some serious design issues that cause invalid code to be silently accepted by default, which is normally a disaster when it gets to debugging. For MIPS at least, one of the completely wrong design decision has been to map basic register…

Can you report this issue at https://github.com/ARM9/bass/issues/new? I'm not the best one to forward or rephrase it, having not written MIPS using Bass.

Re: SNES Development Part 1: Getting Started

#43
post #7

also check out the bass asembler https://github.com/ARM9/bass and the snes dev kit https://github.com/alekmaul/pvsneslib

I generally advise against using bass for home-brew development. Bass is not a very well thought out assembler. I've never used it for 65816, but for other architectures like MIPS has some serious design issues that cause invalid code to be silently accepted by default, which is normally a disaster when it gets to debugging. For MIPS at least, one of the completely wrong design decision has been to map basic register…

Hi. I cannot belive that I actually registered on this page just to write this comment. But I also got the feeling that there had been alot of mist around of bass, and I hope to lift some of it.

So first thing first: There _is_ and community fork. Url had been spammed allready. Yes we are active. To be honest, bass is more active then it probably ever had been before. Next days we will also launch a project page (url: www.basm.dev). And yes .. that near passed away was as least a shock for us. But its also the reason why we took it up.

Now about @giovannibajo1 very valid statement: Yes. Until recently that would had been true. Syntax may, or may not always be optimal. It's too sad that so far no Issue ticket, or Discord Message had reached me about this thoughts. In the end its a community project. All I can say at this point is that the pure assembly syntax is to 100% fluid. You can mix it your own flavor. To be honest I never did MIPS using bass myself. But I would love to chat about "how a clean syntax should looks like".

Feel welcome.

Re: SNES Development Part 1: Getting Started

#45

Earlier quoted context omitted.

I generally advise against using bass for home-brew development. Bass is not a very well thought out assembler. I've never used it for 65816, but for other architectures like MIPS has some serious design issues that cause invalid code to be silently accepted by default, which is normally a disaster when it gets to debugging. For MIPS at least, one of the completely wrong design decision has been to map basic register…

Hi. I cannot belive that I actually registered on this page just to write this comment. But I also got the feeling that there had been alot of mist around of bass, and I hope to lift some of it. So first thing first: There _is_ and community fork. Url had been spammed allready. Yes we are active. To be honest, bass is more active then it probably ever had been before. Next days we will also launch a project page (url…

I'm sorry if my comment came across as offensive, it wasn't my intent. I wasn't aware that there was a community fork of bass, and bass used to be pretty abandoned, so I've been advising people against it for quite some time. I'm happy if there's a community willing to reprise development on it.

I will open an issue, and I've joined the discord if you want to discuss about this. I'm happy to help though I've not really used it for years now, but I am happy to at least tell you why I stopped using it so that you can ponder this for future developments.

Re: SNES Development Part 1: Getting Started

#46

Earlier quoted context omitted.

I generally advise against using bass for home-brew development. Bass is not a very well thought out assembler. I've never used it for 65816, but for other architectures like MIPS has some serious design issues that cause invalid code to be silently accepted by default, which is normally a disaster when it gets to debugging. For MIPS at least, one of the completely wrong design decision has been to map basic register…

Can you report this issue at https://github.com/ARM9/bass/issues/new ? I'm not the best one to forward or rephrase it, having not written MIPS using Bass.

Sure, will do.

Re: SNES Development Part 1: Getting Started

#47
post #41
post #18

Earlier quoted context omitted.

A friend of mine from high school is working on a SNES tracker[0]. He’s deep into this space and could probably answer your questions if you catch him on stream[1]. He also authored many of the sections on the SNES development wiki linked by the article (under “bazz”). [0] https://github.com/bazz1tv/snestracker [1] https://www.twitch.tv/Bazz1tv

is this the legendary M Bazzinoti?

The very same :)

Re: SNES Development Part 1: Getting Started

#48

Earlier quoted context omitted.

Hi. I cannot belive that I actually registered on this page just to write this comment. But I also got the feeling that there had been alot of mist around of bass, and I hope to lift some of it. So first thing first: There _is_ and community fork. Url had been spammed allready. Yes we are active. To be honest, bass is more active then it probably ever had been before. Next days we will also launch a project page (url…

I'm sorry if my comment came across as offensive, it wasn't my intent. I wasn't aware that there was a community fork of bass, and bass used to be pretty abandoned, so I've been advising people against it for quite some time. I'm happy if there's a community willing to reprise development on it. I will open an issue, and I've joined the discord if you want to discuss about this. I'm happy to help though I've not real…

sounds good :)
Post reply on HN