Author Topic: Multiprocessor / Multi core programming using C (Read 788 times)

ManNoy VillAquino · « **on:** August 05, 2009, 10:53:23 PM »

Though we are used to the usual sequential instruction execution, may it be in interrupt thread or main thread, I'd like to know how other engineers develop firmwares for multicore chips. Basically, the usual RTOS knowledge in using semaphores and or mutex are still applicable, how do other engineers approach this kind of set-up? Any tips and or suggestions? Thanks.

Philippine Electronics Forum · « **on:** August 05, 2009, 10:53:23 PM »

ManNoy VillAquino · « **Reply #1 on:** August 09, 2009, 08:16:39 AM »

wala...

busy sa pag gawa ng projects nila. ehehe...

Philippine Electronics Forum · « **Reply #1 on:** August 09, 2009, 08:16:39 AM »

ManNoy VillAquino · « **Reply #2 on:** August 19, 2009, 01:59:41 PM »

Semaphores and Mutex... needed for synchronization

Philippine Electronics Forum · « **Reply #2 on:** August 19, 2009, 01:59:41 PM »

insomartin · « **Reply #3 on:** August 19, 2009, 02:12:46 PM »

i have a cnc here running in multicore
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Latency-Test

some madmen at linuxcnc runs the thread on 1 core then the other one for display and preprocessed math computations. since the servo runs on a very very high speed (counting encoder inputs, DRO, multi axis servos (which should run totally parallel) a much needed everything must be in-sync...

Philippine Electronics Forum · « **Reply #3 on:** August 19, 2009, 02:12:46 PM »

insomartin · « **Reply #4 on:** August 19, 2009, 02:18:19 PM »

http://www.isd.mel.nist.gov/projects/rtlinux/rtutorial-2.0/doc/tutorial.htm

Philippine Electronics Forum · « **Reply #4 on:** August 19, 2009, 02:18:19 PM »

ManNoy VillAquino · « **Reply #5 on:** August 19, 2009, 02:36:31 PM »

Thanks...

sounds easy if you only have a servo and a display for a multi core chip?
sorry, haven't seen the link yet.

kernel_panic · « **Reply #6 on:** August 21, 2009, 12:25:33 PM »

BIOS?

kernel_panic · « **Reply #7 on:** August 21, 2009, 12:50:30 PM »

i say dont unlock the resource until you are sure you are finished using the resource, i think that locking the whole subroutine that has access to the resource is better, it might be slower but safer. or redesign the system, reduce the number of shared resources as much as possible.

insomartin · « **Reply #8 on:** August 21, 2009, 04:11:02 PM »

Quote from: MultiCore_user on August 19, 2009, 02:36:31 PM

Thanks...
sounds easy if you only have a servo and a display for a multi core chip?
sorry, haven't seen the link yet.

it is easy...

cause i'm running one. on your end, it might be you're on your own.

Philippine Electronics Forum · « **Reply #8 on:** August 21, 2009, 04:11:02 PM »

Philippine Electronics Forum