Matrix user forums

Hi, It looks like a (small) error in the flowcode definition. At least, looking at the processor definition IOC is defined, IOCB is not. You could try changing iocb to ioc (multiple times) in 12F675.fcd (directory Program Files\Matrix Multimedia\Flowcode V3\fcd) Or wait for Ben or Steve to provide t...

jadiflow wrote: wpua = 0b00110111; //wpua on all

The wpua... line generates a compiler error. I checked the 16F684.fcd and didn't find anything on the weak pullup register. Is this not implemented in the F684?

Jan,

It looks like it is called WPU, not WPUA in the definition for this processor.

Good luck,

Jac

The discussion at http://www.matrixmultimedia.com/mmforum ... =21&t=6356 probably answers your question.

Hi, In the USBSlaves SlaveProperty TAB one has to specify a Slave Service Macro Name, even when no slave service is being used. If no macro name is supplied the code generated for FCD_USBSlave0_Start_Slave_Service is invalid. Without a macro name there are a lot of FCM_(...params...) calls in the ge...

Hi, pic_usb.h defines req_Set_Interface. However in pic_usb.c it is not used as it should be in usb_handle_standard_request. As a result the (Linux at least) USB stack waits a couple of seconds when trying to close a USB connection as it does not receive a reply to the request and has to wait for a ...

Hi, Suggestion to rename the Start_Slave_Service of the USBSlave component to Run_Slave_Service or something along those lines. Start suggests (at least to me) a function spending a finite amount of time within the function. Looking at the code of Start_Slave_Service it becomes obvious it will not r...

I will look into why the details are not being displayed correctly with the USB slave component. Hi Ben, Did you get around to look at the issue with the details not being displayed? Looking at the code in usb_config_dll.c (usb_get_descriptor_callback): case 00: descriptor_size = sizeof(string_00);...

Ben,

I'll get back to you regarding my sample code. Have to clean it. There is some example code available on the internet, http://www.varxec.net/picdem_fs_usb/fsusb_demo.c for instance.

Ben, The information not being available seems to have something to do with it being declared "rom char *MX_...". If I change usb_config_dll.c to use a static or const char array for the MX_... and hard code the length (or use array element 0 as it contains the length) the information becomes availa...

Hi Ben, The DLL is not used on Linux. The information 'lsusb' normally uses is stored in a text file on the system (manufacturer id and device id information). In the verbose mode lsusb requests additional information from the device. That is the information stored in the unicode strings as set in t...

Hi Ben, There is no need for a driver to be able to show information on connected devices on Linux. The OS has a convenient 'lsusb' command to list information on devices connected. To be able to talk to the simple function I've implemented I'm using libusb with a simple C program. So there is no ne...

Hi, Created a very simple program with the USB Slave. Used the properties of the component to set the 'Name' and 'Manufacturer'. When I connect the device to a Linux box the values are not shown, the output is: bcdDevice 0.01 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Where I expect t...

Hi,

After updating Flowcode (for PIC) to 3.6.11.53 using the 3.4/3.5 updater code using the USB Slave component does not compile. The error is caused by a typo on line 375 of USBDlave_code.c, it reads '#els' and should be '#else'.

Best regards,

Jac

Steve,

While trying to create a simple example I found I wasn't able to call the macro with an array. I did not notice this before because the code I have been working on calls the macro from custom_code so the caller is in C code, not the graphic program flow.

Best regards,

Jac

Hi Steve, Actually, I found a way to pass arrays to a macro: * First define the array parameter with a size. (a[10]) * Next create the code in the macro, this step needs the array size to include all element directly accessed (something like a[3] == 1 requires the array to be defined with at least 4...

Hi, When creating a macro with an array (of bytes) as parameter flowcode generates code the preprocessor does not accept. In the generated c code (lines 50+51): //Macro function declarations void FCM_testMacro(char FCL_DATA[10]); This generates the following errors when trying to generate a HEX file...

Hi again! Solved the issues listed in my previous message. According to the beta components page: Note: The ECIO definition files that come with Flowcode V3.2.2 do not include the USB interrupt function. Therefore if you are using V3.2.2 or earlier of Flowcode you will need to replace the ECIO FCD f...

Hi, I'm trying to create an USB application based on the USB_Mouse example provided in the beta components. After adding the usb_defs.h file to the correct directory I'm able to generate a hex file, however looking at the generated c code I noticed the following lines: //Start USB interrupts //Inter...

Hi Ben, Thank you for supplying the file. The USB example code in the beta components section did not compile when I commented the references to usb_defs.h. After copying the file to C:\Program Files\Matrix Multimedia\Flowcode V3\boostc\include flowcode generates the hex file succesfully. Best regar...

Hi Steve,

I'm looking at the HIB USB example, however it includes usb_defs.h which can't be found on my system. Is there anything I need to install to get this file (and probably other parts needed for USB as well) ??

Best regards,

Jac