Initialize I2C in CORE_M0

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

Initialize I2C in CORE_M0

525件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by vinod9990 on Sun Oct 19 00:49:23 MST 2014
Dear all,
I am working on LPC4350FET256 Dual core micrecontroller (CORE_M4 and CORE_M0) with base code "lpcopen_2_12_keil_iar_hitex_eva_4350" on freertos_blinky code.
I want to use I2C0 in CORE_M4 and I2C1 in CORE_M0. I initialize I2C0 and I2C1 in CORE_M4 code. After porting CORE_M4 and CORE_M0 image into SPI flash, at the time of Run CORE_M4 code stop working.
Where should i initialize I2C1 code to use in CORE_M0.
ラベル(1)
0 件の賞賛
返信
2 返答(返信)

504件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by vinod9990 on Fri Dec 12 22:31:23 MST 2014
Thank you Sir.
0 件の賞賛
返信

504件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by hangdog on Fri Oct 31 07:15:59 MST 2014
I haven't used the I2C peripherals, but afaik it makes no difference which core you use to interact with a peripheral, at any stage. It's not like an OS, where threads have resources associated with them. They're just raw cores, talking to the bus (or buses), the bus mediates requests, and those requests reach the peripherals. The peripherals know not which core is asking. As to "porting" into flash, and "stop working", well I guess we'd need more information. If your "porting" consisted of moving the code in the memory map, then is your code position independent?

Cheers
0 件の賞賛
返信