不使用HIB_XTAL怎样才能终止

搬到村田社区，加入伊努托姆罗伊1742091



     以下为原文
  Moving to the Murata community, adding inoue_tomohiro_1742091

HIP LPO SEL的RAP和陷阱不应影响，因为这些都是由SW覆盖的。Hibl LPosiSel-Pin应该保证你得到的是32千赫时钟的来源。默认情况下，它是在外部XTAL和内部振荡器之间自动选择的。如果你只有内部振荡器，那么HiByLoPosi-SEL是无用的。此外，当在平台上进行LPO源定义时，这种拖动也被SW覆盖。
重要的是LPO源在平台上的错误配置。如果有XTAL填充，如果平台已经使用ILPO定义，设备将不会启动。这也同样适用。在Label.C中定义BLL使用内部RC OSC或外部XTAL配置LPO
内部RC振荡器=
外部XTAL或TCXO＝PuxFrimeHiBiangnistcCurLouthExcel
const PultFixHiBiBeNixt HiBieldIsconFig＝{
时钟= PrimFixHiBiBeNixCixLangIngal32 kHz，
HibxExtCyLogyFrq＝0，/*使用默认设置*/
RCX代码= PrimFuthHibWaKeY-cTrLGReGr.RcCal码，
}；



     以下为原文
  Pull's and traps for HIB LPO sel should not affect, since these are anyway override by SW. HIB_LPO_SEL pin is supposed to *guarantee* which source you’re getting for the 32kHz clock. By default it’s auto selected between the external xtal and the internal oscillator. If you have only the internal oscillator then HIB_LPO_SEL is useless. Also this pull is over ride by SW when making LPO source definitions in platform.c.
 
The thing what matter is wrong configuration of LPO source in platform.c- if you have XTAL populated the device wont boot-up if platform.c have defined using iLPO. This works also vice-versa. Bellow definition in platform.c to configure the LPO either using internal RC-osc or external XTAL
 
Internal RC oscillator = PLATFORM_HIBERNATION_CLOCK_INTERNAL_32KHZ
external XTAL or TCXO = PLATFORM_HIBERNATION_CLOCK_EXTERNAL
 
const platform_hibernation_t hibernation_config = {
    .clock              = PLATFORM_HIBERNATION_CLOCK_INTERNAL_32KHZ,
    .hib_ext_clock_freq = 0, /* use default settings */
    .rc_code            = PLATFORM_HIB_WAKE_CTRL_REG_RCCODE,
};

嗨，雅卡珊，
非常感谢您的帮助。
当我们在软件中定义ILPO时，我们可以将HibxxTalpII/OUT作为打开吗？
当做



     以下为原文
  Hi jaka san,
 
Thank you for very helpful information.
When we define iLPO in the software, can we leave HIB_XTAL_IN/OUT as open ?
 
Regards

你好，
是的，在32 K XTAL被删除后，引脚可以左浮动/打开。虽然对于第一个原型，我建议你至少有一个32 K XTAL的着陆模式，并为Hibl LPosiSelL拉上电阻着陆模式。这是因为你可以通过控制组件逐个地带走组件来优化组件计数，同时验证功能。
我已经看到了32 K XTAL移除与许多其他更改并行进行，然后无法知道对最终结果的影响。
干杯
贾科科



     以下为原文
  Hi,
 
Yes, after the 32k XTAL is remove the pins can be left floating/open. Although for first proto I would recommend you have at least landing pattern for the 32k XTAL and Pull UP resistor landing pattern for HIB_LPO_SEL. This is for the reason you can optimize component count by take components away one-by-one in controlled way, meanwhile verify the functionality.
 
I have seen 32k XTAL removal done parallel with too many other changes then cannot tell which change affected to the end result.
 
Cheers
Jarkko

嗨，哈尔科桑，
我们成功地启动了软件定义乐柏为你写的。
我们的董事会模式的落地水晶hib_xtal_in /但
HibxxTalpIIN /OUT现已开放。
谢谢你的回答和帮助。
当做



     以下为原文
  Hi jarkko san,
 
We succeeded to boot up by defining iLPO in the software as your wrote.
Our board have the landing pattern of crystal to HIB_XTAL_IN/OUT but both
HIB_XTAL_IN/OUT are open now.
 
Thank you for your answers and helps.
 
Regards