one of my customer made a spc5775board,he did not bull down ether of the boot config pins,

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

one of my customer made a spc5775board,he did not bull down ether of the boot config pins,

Jump to solution
642 Views
steven_zhang
Contributor V

one of my customer made a spc5775board,he can not connect his board to a PC with a muli-link ,  should the BOOTCFG pins be pull down to the GND?

0 Kudos
1 Solution
628 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

This device exist only in 416-pin version that does not have BOOTCFG[0] and defaults to zero. BOOTCFG[1] needs to be grounded if MCU is supposed to boot from internal flash memory.

Another option is to program Miscellaneous DCF record to choose right booting options. Pay attention to following tools (use MPC5777C DCF Configurator):
https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/MPC57xx-DCF-records/ta-p/1114884

In such case having BOOTCFG[1] untreated would not cause any issue. Just noting programming of DCF records is not trivial task - user can easily destroy the chip. Please read carefully all instruction to understand the procedure correctly.

 

View solution in original post

0 Kudos
1 Reply
629 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

This device exist only in 416-pin version that does not have BOOTCFG[0] and defaults to zero. BOOTCFG[1] needs to be grounded if MCU is supposed to boot from internal flash memory.

Another option is to program Miscellaneous DCF record to choose right booting options. Pay attention to following tools (use MPC5777C DCF Configurator):
https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/MPC57xx-DCF-records/ta-p/1114884

In such case having BOOTCFG[1] untreated would not cause any issue. Just noting programming of DCF records is not trivial task - user can easily destroy the chip. Please read carefully all instruction to understand the procedure correctly.

 

0 Kudos