Is there a way to define "data" in pv2ass?
This is really for BillW, but I'm posting it publically, since the answer might be useful. I am trying to "assemble" my disassembled code from the 6550. To do this, I need to insert specific data into specific regions (specifically, the jump tables and filenames) The idea is that I can create a set of assembly files which will "recreate" the 6550 FW - but allow things like breakpoints or -*test*-('") "jigs" in it. That and it is greatly helping me trace the code. I have got all the .orgs in for bank0 so that it compiles, and I can even run disv8 on the output and the code matches - but the data regions are still empty. I've looked through the documentation, but found no obvious way to place arbitrary data at arbitrary locations. Did I miss something? Thanks! -radarman

Checkout README.2.PV2ASS.txt and search for the .DSB directive. There's an example there, and brite_eye has some sample code in his sdram example here: http://camerahacking.mine.nu/phils/demanufacturing/pv2/www/brite_eye/sdram.s

I can define data fine using .DB and .DSB, however I am still trying to work out how to read a sequence of data with loop. When I run my program in the simulator, it successfuly reads the data, but when run on the camera it seems to be doing something else...like maybe reading data from a different location.

Radarman, sorry, my brain was on autodrive before. .DB would be better for arbitrary data. Zapped, just saw the code in the other thread - I'll give it a once over tonight and see if I can track down the problem.

Yep, I figured that out after a bit. Makes things a lot handier when you can: .DB $00,$01,$02... I essentially recreated the data portions by just inserting the required characters from the dump.