omap - Ducati for OMAP5 -


i'm quite familiar ducati framework omap4. i'd know if there difference in ducati framework omap5. because, in omap4, had viewed trace logs - trace0 , trace1. but, in omap5, trace0 available. there not documents available on online.

this isn't omap4 vs omap5 difference. ducati subsystem made of 2 arm cortex m cores (2xm3 on omap4, 2xm4 on omap5). initial implementation of rtos (on omap4) did not support smp, each m core running own rtos instance, , own image. each core indeed running different image loaded remoteproc.

the trace0 , trace1 refered running cortex m core id, each image using different id. mpu side send messages either 1 or other core, explicitly.

the rtos running on ducati cores (aka ti sys/bios) later improved , support smp added. android omap 'releases' transition happened in omap5 timeframe. rtos on omap5 android release running single image aware of 2 cortex m cores, , able schedule tasks on 1 core or other. consequence there single 'trace' instance (trace0). mpu 'see' ducati single subsystem, , send messages instance (instead of sending either core0 or core1). messages on ducati subsystem dispatched right task/thread running on 1 core or other.

i said wasn't omap4 vs omap5 difference, since smp aware sysbios available on omap4 @ point (as in non android linux releases).


Comments

Popular posts from this blog

commonjs - How to write a typescript definition file for a node module that exports a function? -

openid - Okta: Failed to get authorization code through API call -

thorough guide for profiling racket code -