UK Vintage Radio Repair and Restoration Discussion Forum - View Single Post

SiriusHardware · 24th Jan 2023, 9:12 pm

I look forward to seeing that.

In the meantime has anyone noticed a way to specify an execution address for SBASM3 to include in the output file as an 'execution address' record?

If SBASM3 actually supports the generation of the correct type of record in an Intel Hex file I will consider adding it to the Pi-uploader (send14) script as an alternative way of specifying the execution address.

Edit: Looking at the list of SBASM3 directives here:-

https://www.sbprojects.net/sbasm/directives.php

I don't see any way to get SBASM3 to generate an execution address record (or 'linear start record') in its Intel Hex file output.

In any case the information given here

https://developer.arm.com/documentation/ka003292/latest

seems to imply that the type '05' record type only occurs in files targeting 'MDK-ARM only', whatever that means. The apparent lack of a universal / general way of specifying a 16-bit start address in a 'normal' Intel hex file may have been what led me to adopt the approach I did.

24th Jan 2023, 9:12 pm	#125
SiriusHardware Dekatron Join Date: Aug 2011 Location: Newcastle, Tyne and Wear, UK. Posts: 11,548	Re: Yet another MK14 tape interface (ESP32). I look forward to seeing that. In the meantime has anyone noticed a way to specify an execution address for SBASM3 to include in the output file as an 'execution address' record? If SBASM3 actually supports the generation of the correct type of record in an Intel Hex file I will consider adding it to the Pi-uploader (send14) script as an alternative way of specifying the execution address. Edit: Looking at the list of SBASM3 directives here:- https://www.sbprojects.net/sbasm/directives.php I don't see any way to get SBASM3 to generate an execution address record (or 'linear start record') in its Intel Hex file output. In any case the information given here https://developer.arm.com/documentation/ka003292/latest seems to imply that the type '05' record type only occurs in files targeting 'MDK-ARM only', whatever that means. The apparent lack of a universal / general way of specifying a 16-bit start address in a 'normal' Intel hex file may have been what led me to adopt the approach I did. Last edited by SiriusHardware; 24th Jan 2023 at 9:27 pm.