RamLatches.DoCmd("N",0,0,0) ' led on
RamLatches.DoCmd("F",0,0,0) ' led off
The proper way to debug this is with a can of freezer spray but it is a bit expensive so I've never bought a can. Quicker just to mindlessly resolder joints.
catalina othello.c -lc -D DRACBLADE
catalina test_time.c -lc -DCLOCK -D DRACBLADE
C:\Program Files\Catalina>catalina -D DRACBLADE test_suite.c -lc
Catalina Compiler 2.3
Homespun Spin Compiler 0.27
parsing C:\Program Files\Catalina\target\lmm_default.spin
parsing C:\Program Files\Catalina\target\Catalina.spin
parsing C:\Program Files\Catalina\target\Catalina_Common.spin
parsing C:\Program Files\Catalina\target\Catalina_LMM.spin
parsing C:\Program Files\Catalina\target\Catalina_HMI_Plugin_HiRes_Vga_No_Mouse.
parsing C:\Program Files\Catalina\target\Catalina_comboKeyboard.spin
parsing C:\Program Files\Catalina\target\Catalina_VGA_HiRes_Text.spin
catalina test_sd.c -lcx -T..\target -D DRACBLADE
So - when you have some PASM code, if you load it into a cog is there now a redundant copy of that code in hub?
The bit I don't quite understand is transferring data between hub and cog. If it is compiled as one big program, I presume the compiler then puts links in so when you read and write bytes from within PASM code it reads from the right place. eg a rdlong.
But if you (say) compiled that PASM DAT section as a seperate module, and then had a rdlong instruction, how would it know to get the long from the right place? Especially as the hub code might change over time. Would you have to rewrite the code to transfer data via a fixed location eg some longs at the top of memory?