IPC chicken-and-egg problem

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

IPC chicken-and-egg problem

ソリューションへジャンプ
1,707件の閲覧回数
Class_Five
Contributor II

I'm designing a system to use IPC among two or more copies of the same hardware running the same set of tasks. The intent is for each copy of the HW to determine its unique identity (processor number) from a database stored in a removable device, e.g. USB memory stick, prior to creating the IPC component. In other words, I want to use MQX services (USB host) to determine the processor number.

 

However...the processor number has to be supplied when MQX starts. So my question is, Is there a way to change the processor number after MQX starts (and before IPC is created)?

 

Thanks.

0 件の賞賛
返信
1 解決策
1,151件の閲覧回数
Class_Five
Contributor II

For anyone who is interested, I think I can answer my own question now, and the answer appears to be 'no'. During startup MQX takes the processor number from the initialization structure and disperses it in several areas. I don't think there is any practical way to update what is done during startup with a new processor number.

元の投稿で解決策を見る

0 件の賞賛
返信
1 返信
1,152件の閲覧回数
Class_Five
Contributor II

For anyone who is interested, I think I can answer my own question now, and the answer appears to be 'no'. During startup MQX takes the processor number from the initialization structure and disperses it in several areas. I don't think there is any practical way to update what is done during startup with a new processor number.

0 件の賞賛
返信