EK-LM3S6965 provide keil example (such as LWIP)

[craigtao]

EK-LM3S6965 provide keil example (such as LWIP)

Could you offer some example in Keil ?

because so many student still use EK-LM3S6965 in our school,

thanks very much,

[quantum-leaps]

The requested example: qpc/examples/lwip/arm-cm/lwip_ek-lm3s6965 has been extended for KEIL MDK (with compiler 6). Specifically, the following directories have been added:

• qpc/examples/lwip/arm-cm/lwip_ek-lm3s6965/qk/armclang
• qpc/examples/lwip/arm-cm/lwip_ek-lm3s6965/qv/armclang

As described in the README.txt files in those directories, the uVision projects require the Software Pack Keil::LM3S_DFP, which is available from:

• https://www.keil.arm.com/packs/lm3s_dfp-keil/devices/

The Software Pack needs to be downloaded and then imported into KEIL uVision.

The support for KEIL compiler 6 required also some minor tweaks to the qpc/3rd_party/ek-lm3s6965 and qpc/3rd_party/lwip folders. Therefore, it is most convenient to check out the latest version of qpc (or qpcpp) framework from GitHub with the following commands:

git clone https://github.com/QuantumLeaps/qpc --recurse-submodules --depth 1

or for QP/C++:

git clone https://github.com/QuantumLeaps/qpcpp --recurse-submodules --depth 1

--MMS

[craigtao]

@quantum-leaps

thanks so much,

and also EK-TM4C123GXL very popular in our school other group,

Their group participated in the National Electronic Design Competition, using this evaluation board, and they tried to use ThreadX, but our example only had IAR project, no keil project,

I hope you could also help this group.

[craigtao]

@quantum-leaps thanks for helping again

[craigtao]

@quantum-leaps

there has a bug, when set the code as: #define LWIP_DHCP 0

variable name need modify from gwaddr to gw

[quantum-leaps]

The reported issue in 3rd_party/ek-lm3s6965/lwip_driver/netif/eth_driver.c has been fixed. The updated qpc and qpcpp repos have been updated to the latest 3rd_party sub-module. Please check out from GitHub.
--MMS

[craigtao]

@quantum-leaps
the keil project under the path:
it will cause a compile error
error info. : armclang: error: no such file or directory: '../../../../../../src/qs/qs_rx.c'

need to remove this file in QP directory

only in c version

[craigtao]

cpp version also cause error " undeclared identifier 'gwaddr' " when #define LWIP_DHCP 0

if I can commit source code, I'm very happy to fixed it 🙂

[quantum-leaps]

The reported error "error: no such file or directory: '../../../../../../src/qs/qs_rx.c'" occurs only when you attempt to build the Spy configuration (the lwip-spy target in the uVision project). This is NOT an omission but rather is expected because starting from QP 8.0.0, the QS software tracing component is no longer distributed under the open source GPL license (and is NOT included in the open-source distribution). Please see the description of "QP/C Extras".

--MMS

[quantum-leaps]

The LwIP example in QP/C++ has been corrected as well. Please check out the qpcpp repo again.

--MMS

[craigtao]

yes. I know the spy configuration couldn't build successful,
but this error also will be occurred when under the lwip-dbg and lwip-rel.

so, it passed the build when I remove this file from the project.

[craigtao]

I am very much looking forward to you adding keil project to EK-TM4C123GXL threadx example.

thanks

[quantum-leaps]

The missing QS file qs_rx.c in qpc\examples\lwip\arm-cm\lwip_ek-lm3s6965\qk\armclang has been fixed. The problem was that this file was mistakenly in the QP group, whereas it should have been in the QS group, which was excluded in the lwip-dbg and lwip-rel build configurations. This was the only project with this issue. The LwIP example for the QV kernel was correct. (BTW, I could not see the problem because I've built it against full QP, including the QS component).

The fix is pushed to GitHub, so please check out the qpc or qpcpp repos.

--MMS

[quantum-leaps]

Regarding the KEIL project for EK-TM4C123GXL with ThreadX, I've looked at this and it all is quite straightforward. The only problem is the conflict between the module tx_initialize_low_level.s from ThreadX and the startup code startup_TM4C123GH6PM.s from qpc\3rd_party directory. This is quite typical situation, which has really nothing to do with the QP framework itself, but has all to do with the integration of the 3rd-party components.

--MMS