Started by arnoldemu, 21:52, 20 January 16
0 Members and 2 Guests are viewing this topic.
Quote from: arnoldemu on 12:57, 29 October 17Ok I will fix this.
Quote from: cpcitor on 22:32, 01 November 17Severity: current arnoldemu cannot be used for audio work here, or even games, as audio is too awful.
Quote0163 KL NEW FRAME FLY016A KL ADD FRAME FLY0170 KL DEL FRAME FLY0176 KL NEW FAST TICKER0I7D KL ADD FAST TICKER0183 KL DEL FAST TICKER
BD19 MC WAIT FLYBACK
BDD9 TXT OUT ACTION
00001000 cpc_run_address crt0 00001006 _main 00_main 000010A9 _config_gui_init config_gui 000011B9 _cf_rungame controller 000012D6 _key_to_action controller 000012E8 _cf_grid_init model 00001512 _cf_model_init model 00001649 _walkTillObstacle model
Quote from: cpcitor on 11:06, 07 November 17The disassembly and memory windows are interesting trace tools.Need for efficient disassembly/tracing.When tracing through rom, or simply debugging calls involving well-known addresses, one often has to lookup addresses found in ROM code (code addresses, data adresses, firmware entry points in RAM, jump blocks in upper RAM). I did it this morning and ended up asking Google things like "Amstrac CPC BDD9" every other ASM line :-).Also, this happens when stepping through one's code. For example, I had to step into running code generated by SDCC to solve difficult bugs. SDCC provides complete symbol list yet disassembly window does not know about them. Having the information displayed would be a great time saver and enhance the disassembly window tremendously!Tracing through ROM or other programs would make much more sense: when landing on any address (especially after a CALL, JP, RET) you know where you are.....
Quote from: arnoldemu on 11:47, 07 November 17See the Labelmanager (access it via the dissassembly menu). You can also add labels from this menu.You can import symbols from noi (sdcc), pasmo and other assemblers.Does this do as you need?For timings there are instruction timings (see dissassembly menu) that can be enabled.Function timing is available at head revision but give me a couple more days to clean up after the big merge I did.
# ASM sourceLD DE,0
# disassembly with current codeLD DE, s_IRRELEVANTLABEL
# ASM sourceLD (LABEL),ALD (LABEL+4),ALD (MYVECTOR+1),HL
# disassembly with current code, not clear at allLD (LABEL),ALD (&1234),ALD (&BDD4),HL
# disassembly with current codeLD DE, s_IRRELEVANTLABELLD (LABEL),A
# Better resultLD DE, 0 # 0=s_IRRELEVANTLABELLD (&1230),A # &1230=LABEL
# Better retulsLD (&1230),A # &1230=LABELLD (&1234),A # &1234=4+LABELLD (&BDD4),HL # &BDD4=1+TXT_WRITE_CHAR
# ASM sourceLD (LABEL),ALD (LABEL-5),A
# disassembly with current code, not clear at allLD (LABEL),ALD (&6784),A
# Better result: one sees that the second write is 5 below the firstLD (&6789),A # &6789=LABELLD (&6784),A
Page created in 0.093 seconds with 41 queries.