I have a SK-S7G2. I initially used SSP V1.5.2 for a proof-of-concept. The experiment went well and now we have assembled our a hardware prototype based on SK-S7G2 but with subtle changes. Following have changed:
I had previously asked in a post on this forum itself about how to create a BSP for custom board, and it was answered to my expectations.
Now that I foresee a lot of application-level requirement changes, I am keen to know whats the recommended way of moving on with it.
My requirements are as follows:
I see that the SSP1.6.0 is released. Is it advised to begin with SSP 1.6.0 (and the official supported version of e2 studio for SSP 1.6.0)?
The question arises because there has been no documentation for creating a BSP for custom board using SSP V1.5.0 and an older document which guides about the process for SSP V1.2.0 onward, is no longer usable for e2 Studio V7.2.y or V7.1.y.
In reply to Jeremy:
In reply to WedaPashi:
I don't know if there is a document planned specifically for creating a custom BSP with SSP 1.6.0. The proceedure is basically the same as under e2studio 6, however for SSP 1.6.0 the ethernet PHY code has been broken out. The SSP 1.6.0 release notes details the changes :-
So the custom BSP will now need to contain another file bsp_ethernet.h, and if the board doesn't use a micrel phy (KSZ8081RNB or KSZ8091RNB), then the BSP will also need to contain the PHY related code.
Also, under e2studio 7 the .module_descriptions folder is no longer created in each project. Instead, the XML is stored in a modules folder under the e2studio 7 installation:-
In reply to brian_s:
Nothing changes, a pack file used under e2studio 7 still has the XML stored in a folder called .module_descriptions (this image is from the sx8654 touch controller pack from SSP 1.6.0) :-
It is just that e2studio 7 now stores the XML files in a central folder, rather than replicating them in a .module_descriptions folder in each and every project created, in every workspace.
In reply to OlivierD_Watts:
As previously stated in this thread, from the SSP 1.6.0 release notes :-
So you now need to have the file bsp_ethernet.h in your BSP, in that file define BSP_BOARD_PHY_KSZ8081 and include bsp_ethernet.h in the bsp.h file of your bsp.
As a work around you could define BSP_BOARD_PHY_KSZ8081 in the compiler preprocessor defined symbols :-