Legacy Products

Now Making...

--------------------Configuration: IS12.prj - Debug--------------------

InitManage.c

*** .\Driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

*** .\Driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

main.c

*** .\Driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

*** .\Driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

TaskManage.c

*** .\Driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

*** .\Driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

_ffmc16.c

*** d:\work\seat\source\cs95msm\driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

VCT.c

*** d:\work\seat\source\cs95msm\driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

RLT.c

*** d:\work\seat\source\cs95msm\driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

*** d:\work\seat\source\cs95msm\driver\_ffmc16.h(16) E4077P: #error "The I/O register file of the specified CPU option does not exist"

ADC.c

can you tell me why ? thanks! F2MC-16 Family SOFTUNE Workbench V30L35; MB96F646R MCU

Hello Community,

I'm reading this document:

Microsoft Word - mcu-an-300213-e-v13-16fx_flash_security.doc (fujitsu.com)

In section 2.1 the document sais:

'[...] If the supplied Unlock Key is all 0, the Flash Security cannot be disabled at all.'

My question is: If I set the Unlock Key fully with zeros, then will I be able to perform a Chip Erase with the CYPRESS FLASH MCU Programmer after this full-zero setting is applied?

Thank in advance,

Gabor

Hi, I am about to connect a Touchscreen which uses CYTMA568 through I2C to a custom carrier board with NXP iMX6 Application processor.

The linux is built with openembedded / yocto project (dunfell branch) and uses a customized device tree.

First, the BSP provided by the SoM Manufacturer (Toradex, SoM is Colibri iMX6DL), didn't provide support for this touch controller.

I found the following patch series to add the driver:

https://lwn.net/ml/linux-kernel/20180703094309.18514-1-mylene.josserand@bootlin.com/

I also added a node in device-tree according to the binding documentation like this:

&i2c3 {

     status = "okay";

     [...]

     cyttsp:    cyttsp@24 {

             compatible = "cypress,cyttsp5";

             reg = <0x24>;

             interrupt-parent = <&gpio7>;

             interrupts = <10 IRQ_TYPE_LEVEL_LOW>;

             touchscreen-size-x = <800>;

             touchscreen-size-y = <480>;

             status = "okay";

         };

};

I get the following errors during boot:

[    0.394465] cyttsp5 1-0024: Error on deassert int r=-22

[    0.399802] cyttsp5 1-0024: Fail initial startup r=-19

I can use i2cdetect and i2cread to access the device, but the touch driver isn't loaded properly.