How to Modify the PFE Driver and Compile It into the BSP Image

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

How to Modify the PFE Driver and Compile It into the BSP Image

Jump to solution
1,382 Views
waitewang
Contributor III

Dear Experts

        I am using the S32G-VNP-RDB2 development board with the S32G274A chip. The Yocto environment has been fully set up, and the BSP can be compiled normally. Now I want to try adding some debugging information to the PFE driver.  

        I tried to modify the code under this directory—such as altering existing print statements or adding new ones—but after recompiling with bitbake, there were no changes at all; the print output remained the same. Could it be that I’m looking in the wrong directory?

waitewang_0-1769304200038.png

 

Tags (1)
0 Kudos
Reply
1 Solution
1,260 Views
Joey_z
NXP Employee
NXP Employee

Hi,waitewang

Thank you for contacting NXP support!
It is recommended to first attempt to force the compilation of PFE.

bitbake -c compile -f pfe
bitbake -c install -f pfe
bitbake pfe

Or
bitbake -c cleansstate pfe
bitbake pfe

2. Independently compile the PFE driver and check if the added debugging information is being output normally.
3. Check the startup information of the development board's kernel, and verify whether the PFE version information and the compiled and downloaded PFE version information are consistent.

BR

Joey

View solution in original post

0 Kudos
Reply
1 Reply
1,261 Views
Joey_z
NXP Employee
NXP Employee

Hi,waitewang

Thank you for contacting NXP support!
It is recommended to first attempt to force the compilation of PFE.

bitbake -c compile -f pfe
bitbake -c install -f pfe
bitbake pfe

Or
bitbake -c cleansstate pfe
bitbake pfe

2. Independently compile the PFE driver and check if the added debugging information is being output normally.
3. Check the startup information of the development board's kernel, and verify whether the PFE version information and the compiled and downloaded PFE version information are consistent.

BR

Joey

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2299882%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EHow%20to%20Modify%20the%20PFE%20Driver%20and%20Compile%20It%20into%20the%20BSP%20Image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299882%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EDear%20Experts%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20I%20am%20using%20the%20S32G-VNP-RDB2%20development%20board%20with%20the%20S32G274A%20chip.%20The%20Yocto%20environment%20has%20been%20fully%20set%20up%2C%20and%20the%20BSP%20can%20be%20compiled%20normally.%20Now%20I%20want%20to%20try%20adding%20some%20debugging%20information%20to%20the%20PFE%20driver.%26nbsp%3B%26nbsp%3B%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20I%20tried%20to%20modify%20the%20code%20under%20this%20directory%E2%80%94such%20as%20altering%20existing%20print%20statements%20or%20adding%20new%20ones%E2%80%94but%20after%20recompiling%20with%20bitbake%2C%20there%20were%20no%20changes%20at%20all%3B%20the%20print%20output%20remained%20the%20same.%20Could%20it%20be%20that%20I%E2%80%99m%20looking%20in%20the%20wrong%20directory%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22waitewang_0-1769304200038.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22waitewang_0-1769304200038.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22waitewang_0-1769304200038.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F374154i8D92FEA56DDA228E%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22waitewang_0-1769304200038.png%22%20alt%3D%22waitewang_0-1769304200038.png%22%20%2F%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-2301160%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20How%20to%20Modify%20the%20PFE%20Driver%20and%20Compile%20It%20into%20the%20BSP%20Image%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2301160%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3CSPAN%3Ewaitewang%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20contacting%20NXP%20support!%20%3CBR%20%2F%3EIt%20is%20recommended%20to%20first%20attempt%20to%20force%20the%20compilation%20of%20PFE.%3C%2FP%3E%0A%3CP%3Ebitbake%20-c%20compile%20-f%20pfe%3CBR%20%2F%3Ebitbake%20-c%20install%20-f%20pfe%3CBR%20%2F%3Ebitbake%20pfe%3C%2FP%3E%0A%3CP%3EOr%3CBR%20%2F%3Ebitbake%20-c%20cleansstate%20pfe%3CBR%20%2F%3Ebitbake%20pfe%3C%2FP%3E%0A%3CP%3E2.%20Independently%20compile%20the%20PFE%20driver%20and%20check%20if%20the%20added%20debugging%20information%20is%20being%20output%20normally.%20%3CBR%20%2F%3E3.%20Check%20the%20startup%20information%20of%20the%20development%20board's%20kernel%2C%20and%20verify%20whether%20the%20PFE%20version%20information%20and%20the%20compiled%20and%20downloaded%20PFE%20version%20information%20are%20consistent.%3C%2FP%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EJoey%3C%2FP%3E%3C%2FLINGO-BODY%3E