dhe

@dabone , Is it safe to test the voltage output not under load? Center post positive or negative? Thanks for this kewl new product. Most of my TI transformers buzz because of age, and I'm sure the original PSU could do with a recap.

Thoughts?

Thanks! - I will also look at hexdump on .bin file. fwiw - Windows didn't give me any errors or warning on .072.

My option is, it would be a killer feature!

@HOME AUTOMATION thanks for the tip. I was trying to stay away from org and seg directives, that will be a whole other learning exercise. I have you folks to help me along, I have Classic99 which makes it so much easier to expose the inner working of the 4a then I would with real hardware. I have to wonder, what percent of people purchased the E/A Module with the intent of learning assembly language and just gave up?

Every time I hit a bump with my understanding of an instruction, I document the problem in my dhe's problem assembler program, here is what this example looks like: def X ws bss 32 myval equ >0072 C99BRK DATA >0113 X equ $ lwpi ws * look at mov that caught me up in load interrupt data >0113 mov @myval,@>ff00 * this becomes mov @>0072,@>ff00 - * Move the value @ hex 0072, to the address hex ff00... li r1,myval mov r1,@>ff02 * correct - puts the value of >0072 into r1, move the value 72, into memory * location >ff02 jmp $ Then every couple of weeks, I review my problem child programs.

@dhe - you asked for a way to dump memory then identified the dump memory command I'd like a hex ask dump, something I could then more easily use by cutting and pasting in to an editor.

@InsaneMultitasker what is GenWIPE for? I don't remember seeing that before.

@Tursi write: "You can view the contents of FFFC after loading it to make sure it has the values you expect." Yes, I use Classic99's Debugger all the time to view address for values I'm expecting, the quirky problem for me in this was, I didn't know *WHAT* value I expected as this time, the value was created by where the linker loaded something in memory, vs, something more simple like a FLAG DATA >0001. For a new guy, this was a 3rd order problem. I'm just glad, on my own, I made the connection, that I could trap the interrupt without the need to aorg anything. At three hours of free time a week, I'm still very much at the why didn't this assemble phase! 😃 Next step, without Gary kind help, would have been to look at the list and try to find unique values in memory and then look through the address display and find 'values you expect'. The exercise once again shows how helpful Classic99's debugger is, as a learning tool.

Much appreciated Gary. I suspected as much, I still get twisted around with am I moving the Address or the value at the address. Luckily, sometimes xas99 will come to my rescue. Do you have any recommendations, on how to not make the mistake? Everything works now, as expected:

My Mis-key, using smart programmer example: Changing the code, to >FFFE didn't help.

This is helpful:

I'm trying to incorporate a load interrupt handler in to an existing EA3 program. Traditionally, I've noticed, AORG is used for the thing. @mizapf code is: AORG >FFFC DATA WORKSP,HANDL HANDL CLR @>FFFC LWPI WORKSP LI R0,DELAY DEC R0 JNE $-2 LI R0,WORKSP MOV R0,@>FFFC Doesn't that tell the loader, to start loading all following code at >FFFC? I didn't want to mess with the loading of additional code after >FFFC, I though it would work if I manually primed the two address needed. It doesn't seem to work, when I tell Classic99 to do a load interrupt, my existing program just continues on it's merry way. I don't have a 'real' TI setup to test with. Does a problem with the code jump out at anyone? liwsp BSS >20 Workspace to be used by load interrupt routine. * TI's E/A loader clears the screen for you, and starts in 32 column GRPI mode. X LWPI USRWS limi 0 * >FFFC WP for Load Interupt * >FFFD Start Address for PC mov @liwsp,@>FFFC mov @HANDL,@>FFFD BL @DISFNT .. Later on in the routine, a routine with HANDL is defined. HANDL EQU $ Stuff, More Stuff. JMP $

I think lots of phrase roms can be found here: https://www.s-n-u-g.de/spvmc/index_en.php

See (F10) - Dump RAM You get the whole enchilada in binary. (Both CPU RAM and VDP (in separate files)).