You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I exported a DIR file to process with sad directly, the output was riddled with errors. Where a address range was expected in the argument, the second address was missing the bank on the beginning part of the address. Also, addresses are being output to odd address ranges, that sad also does not like. There may be more errors in the msg file, but I will post all of the files I used and what I did to get the errors.
First, I was trying to combine a newly posted list of DMR files, and and existing XDF using SAD806x. I had converted the DMR csv to DIR file, and was processed with sad with no issues. I then loaded an appropriate bin into SAD806x and the DIR previously mentioned, then loaded a known good XDF for the same strategy, and performed a disassembly inside SAD806x. I then exported a DIR from sad806x to be processed externally with sad. This is where all of the error messages are coming from. I will attach each file used/generated, and all programs were using the most recent builds of each program as of the time of this message.
You have no issue with SAD806x, when disassembling ?
If no, have you tried to select a different SAD version as an option in SAD806x, before exporting DIR file ?
When I exported a DIR file to process with sad directly, the output was riddled with errors. Where a address range was expected in the argument, the second address was missing the bank on the beginning part of the address. Also, addresses are being output to odd address ranges, that sad also does not like. There may be more errors in the msg file, but I will post all of the files I used and what I did to get the errors.
First, I was trying to combine a newly posted list of DMR files, and and existing XDF using SAD806x. I had converted the DMR csv to DIR file, and was processed with sad with no issues. I then loaded an appropriate bin into SAD806x and the DIR previously mentioned, then loaded a known good XDF for the same strategy, and performed a disassembly inside SAD806x. I then exported a DIR from sad806x to be processed externally with sad. This is where all of the error messages are coming from. I will attach each file used/generated, and all programs were using the most recent builds of each program as of the time of this message.
SYM2_dir.txt
sym2_msg.txt
stock_dir.txt
FBFG2_171111.xdf.txt
The text was updated successfully, but these errors were encountered: