S32K146:D-Flash Code burning

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

S32K146:D-Flash Code burning

Jump to solution
2,025 Views
ShaoTianzhi
Contributor II

Hello:

        想了解一下,如果我拿到了一块新的S32K146芯片,在我没有运行过任何程序的情况下,将包含D-Flash区域的.hex文件直接烧写到芯片中,D-Flash区域能写入代码么,还是只有P-Flash地址段能够烧写成功?

ShaoTianzhi_0-1717139135751.png

 

0 Kudos
Reply
1 Solution
1,911 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@ShaoTianzhi

D-Flash的数据掉电也不会丢失,如果丢失一定是被擦除,擦除可能的原因

1.执行了分区操作,每次执行分区都会擦除数据

2.调试器在下载程序的时候,没有设置区域保护,默认会全擦。

View solution in original post

0 Kudos
Reply
3 Replies
1,993 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@ShaoTianzhi

可以,

由于未启用EEPROM机制,整个FlexNVM被分配为D-Flash空间。其中EEPROM状态机存在于设备中,但未激活。此时,FlexNVM的使用特性与datasheet中指定的P-Flash存储器的特性相同。

0 Kudos
Reply
1,935 Views
ShaoTianzhi
Contributor II

如果程序按照BootManager->BootLoader->Application这个工程顺序执行,BootLoader工程不到32K大小,用0xFF将生成的Hex填充成32K,被存放在D-Flash前32K的位置,Application将D-Flash分区为32K EEPBackup,32K D-Flash,烧写后运行一次,可以正常动作,再次上电发现BootLoader程序消失了,再次重新烧写后正常动作,是分区导致BootLoader程序被擦除了么?是BootLoader的Hex文件被填充的太大的原因吗?

ShaoTianzhi_0-1719479466340.png

 

0 Kudos
Reply
1,912 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@ShaoTianzhi

D-Flash的数据掉电也不会丢失,如果丢失一定是被擦除,擦除可能的原因

1.执行了分区操作,每次执行分区都会擦除数据

2.调试器在下载程序的时候,没有设置区域保护,默认会全擦。

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-1878722%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ES32K146%3AD-Flash%20Code%20burning%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1878722%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%E6%83%B3%E4%BA%86%E8%A7%A3%E4%B8%80%E4%B8%8B%EF%BC%8C%E5%A6%82%E6%9E%9C%E6%88%91%E6%8B%BF%E5%88%B0%E4%BA%86%E4%B8%80%E5%9D%97%E6%96%B0%E7%9A%84S32K146%E8%8A%AF%E7%89%87%EF%BC%8C%E5%9C%A8%E6%88%91%E6%B2%A1%E6%9C%89%E8%BF%90%E8%A1%8C%E8%BF%87%E4%BB%BB%E4%BD%95%E7%A8%8B%E5%BA%8F%E7%9A%84%E6%83%85%E5%86%B5%E4%B8%8B%EF%BC%8C%E5%B0%86%E5%8C%85%E5%90%ABD-Flash%E5%8C%BA%E5%9F%9F%E7%9A%84.hex%E6%96%87%E4%BB%B6%E7%9B%B4%E6%8E%A5%E7%83%A7%E5%86%99%E5%88%B0%E8%8A%AF%E7%89%87%E4%B8%AD%EF%BC%8CD-Flash%E5%8C%BA%E5%9F%9F%E8%83%BD%E5%86%99%E5%85%A5%E4%BB%A3%E7%A0%81%E4%B9%88%EF%BC%8C%E8%BF%98%E6%98%AF%E5%8F%AA%E6%9C%89P-Flash%E5%9C%B0%E5%9D%80%E6%AE%B5%E8%83%BD%E5%A4%9F%E7%83%A7%E5%86%99%E6%88%90%E5%8A%9F%EF%BC%9F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ShaoTianzhi_0-1717139135751.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22ShaoTianzhi_0-1717139135751.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22ShaoTianzhi_0-1717139135751.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22ShaoTianzhi_0-1717139135751.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F281901i3986CE61299D90CE%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22ShaoTianzhi_0-1717139135751.png%22%20alt%3D%22ShaoTianzhi_0-1717139135751.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1879338%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3ERe%3A%20S32K146%3AD-Flash%20Code%20burning%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1879338%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CA%20href%3D%22mailto%3AHi%40ShaoTianzhi%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EHi%40ShaoTianzhi%3C%2FA%3E%3C%2FP%3E%0A%3CP%3ECan%2C%3C%2FP%3E%0A%3CP%3ESince%20the%20EEPROM%20mechanism%20is%20not%20enabled%2C%20the%20entire%20FlexNVM%20is%20allocated%20as%20D-Flash%20space.%20The%20EEPROM%20state%20machine%20exists%20in%20the%20device%20but%20is%20not%20activated.%20At%20this%20point%2C%20the%20usage%20characteristics%20of%20FlexNVM%20are%20the%20same%20as%20those%20of%20P-Flash%20memory%20specified%20in%20the%20datasheet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1895039%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3ERe%3A%20S32K146%3AD-Flash%20Code%20burning%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1895039%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EIf%20the%20program%20is%20executed%20in%20the%20order%20of%20BootManager-%26gt%3BBootLoader-%26gt%3BApplication%2C%20the%20BootLoader%20project%20is%20less%20than%2032K%20in%20size%2C%20and%20the%20generated%20Hex%20is%20filled%20with%200xFF%20to%2032K%20and%20stored%20in%20the%20first%2032K%20of%20D-Flash.%20Application%20partitions%20D-Flash%20into%2032K%20EEPBackup%2C%2032K%20D-Flash.%20After%20burning%2C%20it%20runs%20once%20and%20works%20normally.%20After%20powering%20on%20again%2C%20it%20is%20found%20that%20the%20BootLoader%20program%20disappears.%20After%20burning%20again%2C%20it%20works%20normally.%20Is%20the%20partition%20causing%20the%20BootLoader%20program%20to%20be%20erased%3F%20Is%20it%20because%20the%20BootLoader%20Hex%20file%20is%20filled%20too%20large%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ShaoTianzhi_0-1719479466340.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22ShaoTianzhi_0-1719479466340.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F286021iCB05116E5A7FB883%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22ShaoTianzhi_0-1719479466340.png%22%20alt%3D%22ShaoTianzhi_0-1719479466340.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E