Does BASCOM produce ASM output files? If not, how do you handle cases where the output has to be faster than it is, i.e. where it has to take exactly 41.37 microseconds from the time you enter this function until you've returned to the calling procedure? In fact, how well can it handle generating critically timed code? If you have to "get around the loop" in 21 machine-code instruction cycles, how can you ensure that in Bascom?

Hi Richard,

Bascom can produce a number of files, these being pure binary, intelhex, old intelhex, report files with addresses for variables, error file (if any) etc etc.
In your cpu header file, you can tell bascom all about your particular cpu that you code for, this includes clockdiv etc for timing purposes. However, there is a much simpler way which I use, that is to pulse a port pin high at the beginning of a proceedure then pulse it low when finished, then simply measure the time difference on my scope, alternatively one could use the simulator which I have tested personally and found it to be accurate, I still prefer the scope method though.

Darren