Building WP750x CAN drivers


We are trying to build a MCP2515 CAN driver for a Mang-OH green board with a WP7502 module, and have found some instructions on:

However, it is not clear how to build for a WP750x. In the last steps, a mdm9x15-image-minimal image is built, and the file produced is a yocto_wp85.cwe file, presumably for the wp85 model? Can the target module be configured in the earlier steps?

Does anyone here have experience with using a CAN module on a 750x?

We’re using the Legato-Dist-Source-mdm9x15-SWI9X15Y_07.12.09.00.tar.bz2 yocto source.

Best regards,

We have now got the kernel build to run on the WP7502.

presumably for the wp85 model?

In general the wp85 code is compatible with wp750x.

Right now we have some issues in getting the SPI powered correctly, and muxing to IOT Slot 1.

For SPI we get the following lines in logread after the modprobe mcp251x command:

Jun 11 07:13:43 swi-mdm9x15 user.warn kernel: [ 62.887440] spi0.0 supply vdd not found, using dummy regulator
Jun 11 07:13:43 swi-mdm9x15 user.warn kernel: [ 62.892476] spi0.0 supply xceiver not found, using dummy regulator
Jun 11 07:13:44 swi-mdm9x15 user.err kernel: [ 63.926384] mcp251x spi0.0: MCP251x didn’t enter in conf mode after reset

The issue with supply vdd and xceiver is the same as here:

For the mux command, we get some warnings in logread, and the application code never seem to run when it uses the gpioExtender service. The warnings look like this:

Jun 11 08:46:42 swi-mdm9x15 user.debug Legato: DBUG | UNKNOWN[3398]/framework T=main | LE_FILENAME InitPool() 303 | Memory pool name ‘framework.hashMap_refpinSpiEn_ClientHandl’ is truncated to ‘framework.hashMap_refpinSpiEn_C’

We tried building a small application just to do the mux:ing. It runs with the gpioService, but when a binding is added to gpioExtenderService is added, it gives the above warning messages and never runs the COMPONENT_INIT code.