Kinetis MicrocontrollersのトピックRe: I2C works in Debug with Multilink universal, not in standalone

I2C works in Debug with Multilink universal, not in standalone

samc — Tue, 28 Jun 2016 11:08:53 GMT

Hello,

I use the I2C bus of the MKL17Z256VFT4 at 400KHz. When I have the PE Multilink universal connected to the board it works perfectly, when I unplug the Mulitlink it always works but when I restart my board the I2C bus doesn't work. I know my program is running because I do a blink of a LED thanks to a PIT_Interrupt. I have 2 I2C slaves on the bus and no response of the both so I think it's from the MCU.

On BK000001.BMP it's I2C frame when it works and on BL00002.BMP when it doesn't work. This last appears just one time at the start-up of the MCU, after this the bus remains in Vcc State. I think the MCU try a first communication then abandons.

It seems the clock doesn't want to works, SDA fall to "0" but not the SCL.

Sam,

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Wed, 29 Jun 2016 09:22:51 GMT

Hi Samuel,

Could you tell me what the clock source you are using? Internal clock or external crystal?

You said:PE Multilink universal connected to the board it works perfectly, when I unplug the Mulitlink it always works but when I restart my board the I2C bus doesn't work.

Do you mean, just connect the debugger, and don't enter in the debug mode? Or when do debugging the code works ok?

Besides, did you add the external pullup resistor in the I2C_CLK and I2C_DAT pin?

You can send me your project, I would like to help you to check it on my side.

Waiting for your reply.

Have a great day,
Jingjing

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Thu, 30 Jun 2016 07:40:28 GMT

Hi,

- It's an external 12Mhz Crystal.

- It's when I debug the code, it works well. During this debug I unplug the Multilink and it always works.However when I restart my board (electrical reset) it doesn't work (with or without the multilink connected to the board). I did the test without debug mode but just flashing the MCU with KDS too and same result, just after flashing it's OK, when I unplug the probe always OK but after restart : KO.

External pull-up are soldered, it was 8k2 resistors, but rise time was so long and I placed two 1K in parallel for the 2 lines, so equivalent pull-up are 500 ohms for my tests (communication at 400kbits/s).

Can you give me an adress mail to send the project please ?

I hope to resolve this problem rapidly because with this problem 2 important functionnalities of my design are KO, it's bad I need it ASAP.

Thank you,

Sam

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Thu, 30 Jun 2016 08:45:35 GMT

Hi Samuel,

You can attached your project directly.

If it is confidential to you, you can delete all the other important code, just leave the I2C initialize and communication code.

I will test it on my side.

Now please test these points on your side:

1. bus clock frequent checking

Please configure PTC3 as the CLKOUT, and output the bus clock, test it in debug and none debug mode independently.

Whether the bus frequency is changed.

2. Add some delay after power on in the main function, and before the I2C configuration.

For example, add 1 second delay, then test it again.

3. electrical reset, do you mean POR?

Try use the pin reset in PTA4, don't use POR reset again.

Waiting for your reply!

Have a great day,
Jingjing

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Thu, 30 Jun 2016 10:07:12 GMT

1) I don't find how to configure PTC as CLKOUT with PE...otherwise I have a UART Tx chip connected on this pin pulling up the signal to Vcc, it seems not possible to send the CLK here...no ?

2) Delay have no effect...

3) Yest it's a POR. The regulator who supplies the MCU is "Enable or Disabled" by a battery powered hardware.

I tried to pull down PTA4 with no effect. I saw in the datasheet this pin is disabled when boot from ROM, it's my case.

I can't post the complete project so I join a cleaned project. I tested it and he have a different behaviour, it seems that the MCU try to launch an I2C communication permanently without success, the CLK toggles chaotically. I can send the complete project only to a private mail.

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Fri, 01 Jul 2016 09:15:15 GMT

Hi samuel,

CLKOUT configuration, please add this code.

SIM_SCGC5|=SIM_SCGC5_PORTC_MASK;

PORTC_PCT3 = PORT_PCR_MUX(5) | PORT_PCR_PE_MASK_PORT_PCR_PS_MASK;

SIM_SOPT2 = SIM_SOPT2_CLKOUTSEL(2) ;

Then test the PTC3 pin on your board.

About other questions, I will reply you after I check your sample code, please wait patiently.

Thanks a lot for your understanding.

Have a great day,
Jingjing

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Fri, 01 Jul 2016 09:51:48 GMT

Isn't there an error on the second line of the code ? :

- PORTC_PCT3 --> PORTC_PCR3

- PORT_PCR_PE_MASK_PORT_PCR_PS_MASK --> isn'' it a mix of 2 define ? eilther PORT_PCR_PE_MASK or PORT_PCR_PS_MASK ?

I think there will be a conflict with the Tx pin of another chip wonnected at this port but I will try.

EDIT :

I tested with PORTC_PCR3 = PORT_PCR_PE_MASK and I have a Clock at 24 Mhz.

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Fri, 01 Jul 2016 10:09:14 GMT

I think to find the problem. I did a test without bootloader at start and it seems to work...

EDIT : I confirm the problem is when the MCU starts from bootloader!

With this it's OK :

/* Flash Configuration */

.section .FlashConfig, "a"

.long 0xFFFFFFFF

.long 0xFFFF3FFE

With this it's KO :

/* Flash Configuration */

.section .FlashConfig, "a"

.long 0xFFFFFFFF

.long 0xFFFFFFFE

Have I forget everything in the code to avoid this problem ?

So I absolutely need of the bootloader at start.

Re: I2C works in Debug with Multilink universal, not in standalone

scottm — Sun, 03 Jul 2016 05:13:24 GMT

I just ran into something not entirely unlike this when adding a bootloader - my project was proven code migrated from CW6 to CW10 with Processor Expert so everything got shuffled around.

What I discovered is that the linker file specified one entry point and the reset vector pointed to another. Some of the startup code was being bypassed because the debugger apparently starts execution at the entry point as defined in the linker and not at the reset vector. This had me cursing at the system for a good 20 minutes, trying to figure out why my UART was running at entirely the wrong speed.

Scott

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Mon, 04 Jul 2016 08:08:38 GMT

Hi Samuel,

Yes, you are correct, I typed the wrong word, I want to write PORTC_PCR3, it is the type error, it should be:

SIM_SCGC5|=SIM_SCGC5_PORTC_MASK;

PORTC_PCR3 = PORT_PCR_MUX(5) | PORT_PCR_PE_MASK | PORT_PCR_PS_MASK;

SIM_SOPT2 = SIM_SOPT2_CLKOUTSEL(2) ;

But now, you already get the bus clock.

Jingjing

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Mon, 04 Jul 2016 08:13:56 GMT

Hi Samuel,

OK, thank you for your more information.

The main difference is the boot source selection in the FOPT area, 0x40d is the FOPT register data, if you configure it as 0XF3, it means, boot from flash. if you configure FOPT to 11, it means boot from ROOM.

So, you can modify your application code, and let it run from the flash.

Have a great day,
Jingjign

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Mon, 04 Jul 2016 08:14:27 GMT

Hi,

Correction already done, Clock works well. You can find my observation about the bootloader below.

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Mon, 04 Jul 2016 08:44:30 GMT

Hi,

Yes I know I did the test with boot from flash and boot from ROM. The problems on the I2C disappears when I boot from flash but it's not possible for me, I need to boot from ROM to enter Bootloader at startup.

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Mon, 04 Jul 2016 08:49:17 GMT

What the I2C pin you are using?

The same pin withROM bootloader I2C?

Have a great day,
Jingjing

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Mon, 04 Jul 2016 09:32:54 GMT

It's not the same pin as the ROM Bootloader :

- ROM BOOTLOADER :

- I2C0_SDA : Pin 28 (PTB1)

- I2C0_SCL : Pin 27 (PTB0)

- My board :

- I2C0_SDA : Pin 5 (PTE18)

- I2C0_SCL : Pin 6 (PTE19)

I just succed to work the I2C bus with the bootloader, when I deactivate the I2C in the BCA it works well.

I'm surprised to observed this behaviour, the bootloader have to free the I2C bus after bootloading ? no ?

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Tue, 05 Jul 2016 09:38:06 GMT

Hi Samuel,

Actually it is the same I2C module.

Even you want to use the ROM bootloader, you still can configure the FOPT select the code run from Flash.

When you want to run the ROM bootloader, you just need to assert NMI/BOOTCFG0 pin, from the reference manual:

The following conditions will force the hardware to start the Kinetis Bootloader:

• BOOTSRC_SEL field of FOPT register is set to either 0b11 or 0b10. This forces the

ROM to run out of reset.

• The BOOTCFG0 pin is asserted. The pin must be configured as BOOTCFG0 by

setting the BOOTPIN_OPT bit of FOPT to 0.

• A user applications running on flash or RAM calls into the Kinetis Bootloader entry

point address in ROM, to start Kinetis Bootloader execution.

So you can choose the NMI pin as the ROM bootloader enter pin, then you still can run the code from flash.

You can try it on your side.

Have a great day,
Jingjing

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Mon, 11 Jul 2016 07:50:12 GMT

Hello,

I know these informations, so for the moment I just boot from ROM Bootloader and I observe when the I2C peripheral is activated in the Bootloader it doesn't work correctly when switching to user application, I don't know why. This seems not be normal for me.

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Mon, 11 Jul 2016 09:03:59 GMT

I will check it on my side with ROM bootloader.

Now confirm the question again, just the I2C0 in the app can't work after the ROM bootloader downloading the application code?

Other function in the app code still works ok?

Best Regards,

Jingjing

Re: I2C works in Debug with Multilink universal, not in standalone

samc — Mon, 11 Jul 2016 09:10:56 GMT

No problem with other peripheral. For exmaple, I leave the LPUART0 and SPI activated in the ROM bootloader and the two works correctly in my application (I only use LPUART0 to use the bootloader). The SPI works correctly with a flash, no problem with ADC, clockmanager OK, PIT Timer OK

Re: I2C works in Debug with Multilink universal, not in standalone

kerryzhou — Tue, 12 Jul 2016 07:56:41 GMT

Hi Samuel,

I have test it on our FRDM-KL27 board, the chip is MKL27Z64VLH4, this chip has no PTE18,PTE19, so I use PTB0,PTB1 as the I2C0 pin.

My test code is the KSDK2.0_FRDM-KL27, after I use the UART ROM bootloader, my I2C0 still works ok on my side.

I don't know how did you initialize your I2C0 in your application code.

Please disable the I2C0 module at first, then enable it again, this is the I2C initialization code for your reference:

void I2C_MasterInit(I2C_Type *base, const i2c_master_config_t *masterConfig, uint32_t srcClock_Hz)

{

assert(masterConfig && srcClock_Hz);

/* Temporary register for filter read. */

uint8_t fltReg;

#if defined(FSL_FEATURE_I2C_HAS_HIGH_DRIVE_SELECTION) && FSL_FEATURE_I2C_HAS_HIGH_DRIVE_SELECTION

uint8_t c2Reg;

#endif

/* Enable I2C clock. */

CLOCK_EnableClock(s_i2cClocks[I2C_GetInstance(base)]);

/* Disable I2C prior to configuring it. */

base->C1 &= ~(I2C_C1_IICEN_MASK);

/* Clear all flags. */

I2C_MasterClearStatusFlags(base, kClearFlags);

/* Configure baud rate. */

I2C_MasterSetBaudRate(base, masterConfig->baudRate_Bps, srcClock_Hz);

#if defined(FSL_FEATURE_I2C_HAS_HIGH_DRIVE_SELECTION) && FSL_FEATURE_I2C_HAS_HIGH_DRIVE_SELECTION

/* Configure high drive feature. */

c2Reg = base->C2;

c2Reg &= ~(I2C_C2_HDRS_MASK);

c2Reg |= I2C_C2_HDRS(masterConfig->enableHighDrive);

base->C2 = c2Reg;

#endif

/* Read out the FLT register. */

fltReg = base->FLT;

#if defined(FSL_FEATURE_I2C_HAS_STOP_HOLD_OFF) && FSL_FEATURE_I2C_HAS_STOP_HOLD_OFF

/* Configure the stop / hold enable. */

fltReg &= ~(I2C_FLT_SHEN_MASK);

fltReg |= I2C_FLT_SHEN(masterConfig->enableStopHold);

#endif

/* Configure the glitch filter value. */

fltReg &= ~(I2C_FLT_FLT_MASK);

fltReg |= I2C_FLT_FLT(masterConfig->glitchFilterWidth);

/* Write the register value back to the filter register. */

base->FLT = fltReg;

/* Enable the I2C peripheral based on the configuration. */

base->C1 = I2C_C1_IICEN(masterConfig->enableMaster);

}

Please disable I2C prior to configure it, and try again on you side.

If you still have question, please let me know!

Have a great day,
Jingjing