After some experimenting, I figured out how to upload S28 files to the 265SXB with Linux, necessary because the WDC Tools are Windows-only and closed-source. There is a longer version of this with examples at https://github.com/scotws/265SXB-Guide/ ... ng_code.md as part of the 265SXB Guide.

First, you need to install the srec_cat tools (Ubuntu 14.04): This gives you (among other things) the srec_cat tool itself and srec_info to inspect the finished S28 file. For a binary machine code file (mensch.bin) and the output S28 file (mensch.s28) that is to be installed at 00:2000, we need The double "0x2000" looks strange, but the record file isn't complete otherwise (or I'm doing something wrong). More generally, we have (This just begs to be put in a script, obviously, but that's all I have time for today.)

To transfer the resulting file to the 265SXB, press "s" in the Mensch Monitor, and then with (say) minicom, start the transfer as pure ASCII (CTRL-A Z, s, pick "ascii"). Then use "j" to start the program.

Which assembler are you using? Many assembler generate S28 directly so you just need to send the file from your terminal software. Each of the lines in the S28 file starts with an 'S' and triggers the Mensch Monitor to read the rest of the line as an S-record.

_________________
Andrew Jacobs
6502 & PIC Stuff - http://www.obelisk.me.uk/
Cross-Platform 6502/65C02/65816 Macro Assembler - http://www.obelisk.me.uk/dev65/
Open Source Projects - https://github.com/andrew-jacobs

What's an S28 file? I know all about Motorola S-record files, unofficially referred to at times as S19, but not S28. From where did all these weird extensions emanate?

Incidentally, it should be apparent that the S19 moniker comes from the fact that there are 9 record types, not 8.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

> What's S28?
According to Scot's repo:

S19 only supports a 16-bit address. S28 extends it to 24. There is a family of S format records for different size memory buses.

Google is your friend

_________________
Andrew Jacobs
6502 & PIC Stuff - http://www.obelisk.me.uk/
Cross-Platform 6502/65C02/65816 Macro Assembler - http://www.obelisk.me.uk/dev65/
Open Source Projects - https://github.com/andrew-jacobs

My "Tinkerer's Assembler" for now -- one reason I bought the 265SXB is to have actual hardware to validate both that assembler and the Crude Emulator for the 65816 on. The current steps are to figure out how to load programs on the 265SXB from Linux (check), figure out how PUT_CHR and its most important friends function (work in progress), emulate those on the Crude Emulator (to do), and then run more tests comparing the output of the assembler and what the emulator does to what really happens on the 265SXB (lots and lots to do).

Long-term, though, I will probably switch to a more powerful assembler (I think I remember that yours is in Java, which should run on Linux, and includes S28 output) and just write a small tool to convert my beloved Typists's Assembler Notation to whatever that format is. The Tinkerer's Assembler was a fun project and I am very glad I wrote it as a proof-of-concept, but there is no reason to re-invent the wheel, and the mature assemblers out there have all kinds of features it would take months and months to add. I don't really have that time -- there are Forths to code, after all!

Keep settin' us up, big guy, and we'll keep knockin' em down!

http://lmgtfy.com/?q=S28+file



Mike B.

I used this for a reference when I wrote the S19 record support for my Xmodem loader:

http://www.amelek.gda.pl/avr/uisp/srecord.htm

_________________
Regards, KM
https://github.com/floobydust

Ahem...the S-record (aka S19) standard includes 24 and 32 bit addressing. The S19 moniker has to do with the 9 possible records types recognized. It's up to the programmer to decide which ones to use.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

I count 10 records. Did you check Wikipedia?

According to wikipedia, S19 is one possible combination of SRecord records. S19 specifically uses 16-bit addresses, while S28 uses 24-bit addresses (and S37, 32-bit addresses). So, S19 is a subset of the SRecord format, and supports only 16-bit addresses.

https://en.wikipedia.org/wiki/SREC_%28file_format%29#Record_types

Well.. one (S4) is reserved, so there are only 9 to use. But in any case it seems that the general format is really just S-record (and that's how I remember it from the past), and S19/S28/S37 are mostly used to indicate which combination of records are used (well, according to WP - that's new to me).

Edit: quote inserted due to another post arriving in between

Update: So finally I got it.. S19, S28, S37 all need S0 (the header record), but then we have:
S19: Needs records S1 and S9.
S28: Needs records S2 and S8.
S37: Needs records S3 and S7.
All of them: S5 may optionally be used.
Explains the numbering scheme at least. As I said, this is probably not news to many of you.

Thanks for the correction! It seems that BDD has taken the name of a specific flavour to be as good as the name of the format itself. No doubt S19 is the flavour most commonly encountered. "It ain't what you know..."

I skipped S4 because it is reserved.

Also note that S0 is seldom implemented.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Wikipedia's S-record article is in error—S19, S28 and S37 are made-up terms that have never been used by Motorola in the published S-record standard (but have been seen in engineering bulletins, as noted in a following post).

For the definitive description of the S-record format (and terms) please refer to Appendix C (page 640) of the attached manual, which is an official Motorola publication.

Incidentally, the UNIX man page for the S-record format is not entirely correct. Only the Motorola definition should be taken as gospel.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!