FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - FTDI Community

Pages: [1] 2 3 ... 45
1
Hi
Did you try hitting “Pause” in the debug ribbon?
Calculating the peak stack is transfer intensive so I’d bet it would only be performed when it’s stopped running the actual code on the device. 

Regards
FTDI Community

2
Hello,

In reply to your previous questions:

Please try swapping the first two lines of the function around.

Code: [Select]
static size_t strcspn(const char * s1, const char * s2){
    char *c;
    char *s = s1; 
 

The readme file mentions that this might be a problem:

- At optimisation levels of 2 and above, if the first variable declaration in a function also initialises the variable then the initialisation may not occur. Separate the declaration and initialisation of the variable to workaround.

We only put the most basic implementation of the standard libraries that we could.

“A minimal set of C runtime library functions are provided” in the help file.
Further “NOTE: Not all the standard library functions have been included.”

We didn’t know fputc is there as it is not in the help file.

We will not be adding it into the standard libraries as it takes up space and reduces the amount of program space for other code.

We don’t claim to be compliant to any particular implementation of C.

Best Regards,
FTDI Community

3
Test and Review Area / Vinculum II Toolchain Patch V2.0.2-SP3
« on: October 25, 2021, 04:37:54 PM »
Hello All,

We have an update for some VNC2 drivers which include some improvements.

Please contact support1@ftdichip.com and we can send you the installer via SFTP.

Note that you must have V2.0.2-SP2 already installed which can be found here:

https://ftdichip.com/firmware/vnc2-tools/

Vinculum II Installer V2.0.2-SP3.exe will be supplied which is a patch to update all the drivers and libraries (stdio, stdlib etc).

The changes are listed here in the patch readme:

2021-10-25

This is patch Version 2.0.2-SP3 release of the Vinculum II Toolchain, comprising updated device drivers and libraries.

All ReadMe file information applies to the updates provided in V2.0.2-SP3.

*** This patch installer must be applied to an installation of V2.0.2-SP2 only. ***

There are no updates to compile, debug, or other build and configuration tools; sample code; VOS kernel; Vinco libraries; IDE; or documentation.

We welcome suggestions for new features or improvements to existing features.

The ReadMe files for previous releases are also available in the installation directory.
 
Drivers Readme
--------------

Fixed Issues:
- USBSlaveFT232.a fix enumeration issue;
    Add in latency timer get and set IOCTL functions,FTDI_SET_LATENCY_TIMER and FTDI_GET_LATENCY_TIMER were present but not implemented;
    Improve data flow so data is passed faster and more reliably to and from the host;
    Implement a dummy EEPROM to enable applications that require EEPROM checks to work.
- USBSlave.a correct remote wakeup behaviour when acting as a USB device and ensure correct ZLP generation for USB verification tests.
- BOMS.a implement changes for 64kB clusters on FAT16.
- FAT.a fix available cluster count.
- USBHostFT232.a correct baud rate settings for High-Speed devices. Added support for new FTDI devices.
- USBHost.a fix VOS_IOCTL_USBHOST_DEVICE_SET_CONFIGURATION to change the configuration of devices on USB host. Note: this will re-enumerate with the new configuration value.
- USBHostCDC code fix bitmaps for notifications.

Restrictions:
- FAT library will not support ATAPI disks.
- FAT library does not support FAT12 format disks. Please use FAT16 or FAT32 format.
- FAT fat_fileCopy function will only copy files to a different disk from the source disk.
- USBHostFT232 driver does not assert RTS or DTR automatically when flow control is enabled.
    This must be done with an VOS_IOCTL_USBHOSTFT232_SET_RTS/DTR before data can be received.

Known Issues:
- N/A

 
Runtime Libraries Readme
------------------------

Fixed Issues:
- Corrected return value of printf(), sprintf(), fprintf().

Restrictions:
- N/A

Known Issues:
- N/A


Best Regards,
FTDI Community

4
Hi,
Can you provide some screen shots of the issue you are seeing? 
Build settings (Debug/Release) ?   
How big are the stacks for each thread?
Maybe the scheduler has not started? That would need to be running to get the thread manager to show information.
Does it have the current stack size listed?

Regards
FTDI Community

5
Unfortunately the compiler doesn't do all constant initialisation which you might expect on other compilers.

If the values are expressed as constants without typecasting then it will compile.

   
Code: [Select]
enum {
        g0 = 0x82F63B78,
        g1 = (g0 >> 1) & 0x7fffffff,
        g2 = (g0 >> 2) & 0x3fffffff,
        g3 = (g0 >> 3) & 0x1fffffff,
    };
                               
    static const int table[16] =
    {
        0,                  g3,           g2,          (g2^g3),
     g1,       (g1^g3),      (g1^g2),      (g1^g2^g3),
        g0,       (g0^g3),      (g0^g2),      (g0^g2^g3),
        (g0^g1),  (g0^g1^g3),   (g0^g1^g2),   (g0^g1^g2^g3),
   };

I’ve not checked the values in the code though. They are precompiled (in decimal) to the following values according to the ASM output file:

0, 274646895, 549293790, 820201905, 1098587580, 1361435347, 1640403810, 1905808397, -2097792136, -1834419177, -1572096602, -1307217207, -1014159676, -741088853, -483350502, -210866315

Best Regards,
FTDI Community

6
Hello,

Please try renaming the variable from "address" to anything else.

Code: [Select]
typedef signed char                           int8_t;

int t2(int8_t address)
{
    return  0;
}

int t1()
{
                int8_t paramt1;

                t2(paramt1);    //401 - C1406
               
                return 0;
}

Both of these work:

int t2(int8_t badress)

int t2(int8_t baddress)

Best Regards,
FTDI Community

7
Hi,

what programming language are you using? are you able to show a screenshot of your code?

Best regards

FTDI community

8
Discussion - Software / Re: FT602 change resolution
« on: October 06, 2021, 03:18:16 PM »
Hi

Sorry, the only way to change the camera resolution is through the FT602 configuration programmer utility.

Best regards

FTDI Community

9
General Discussion / Re: Ft260q-t instead of ft232r
« on: October 05, 2021, 04:44:38 PM »
Hello,
Link below is for our application note AN_184 - FTDI Device Input Output Pin States.  Page 38 details the FT260 part. 
https://www.ftdichip.com/Support/Documents/AppNotes/AN_184%20FTDI%20Device%20Input%20Output%20Pin%20States.pdf

Regards
FTDI Community

10
General Discussion / Re: Ft260q-t instead of ft232r
« on: October 04, 2021, 04:46:20 PM »
Hello,
Yes, both parts can be used as USB to RS232/RS422/RS485 Converters
https://ftdichip.com/compare-products/?product_cate=18&compare_pr%5B%5D=2074&compare_pr%5B%5D=3757

Regards
FTDI Community

11
Hello,

The SCK line should normally be a push-pull output on this device (unless your code switches the pin to input mode at any time)

What I/O voltage does your MCU use? Is it a 3v3 I/O

We would recommend to check with a scope or logic analyser with analog capability to see what the waveforms are doing,

Best Regards, FTDI Community




12
Hi

Have you made sure to change the EEPROM settings of the device so that it is in self-powered mode? the datasheet states the following:

" Note that in this set-up, the EEPROM should be configured for self-powered operation and the option
“suspend on DBUS7 low” selected in FT_PROG. Also this configuration uses the pin BCBUS7, so this
assumes that MPSSE mode is not selected."

FT_PROG can be downloaded here

Best regards

FTDI Community

13
Discussion - Drivers / Re: VCP driver on macOS 11
« on: September 27, 2021, 01:47:33 PM »
Hello,

That would be the last version of macOS to support .kext drivers, this would be 10.15, but there is an extra notarization step for .kext drivers required by Apple in 10.15, that is not noted in that document. As such it would be safe to assume these instructions work up for drivers up till macOS 10.14.

Best Regards,
FTDI Community

14
Hi

I see the multiplexer you are using has two output channels for each input. are you sure you have configured them correctly, for the clock signal to come out on 2B1? have you tried to see if the signal is on 2B2?

Best regards

FTDI community

15
Hi,

The FT2232H defaults to 2 x UART ports. Using the MPSSE for SPI requires additional commands from the application itself,

The FTDI chipsets are vendor class devices and so require a driver on the host, if you run Linux on the host computer/MCU please ensure the Linux build includes the FTDI driver.

The Linux build may include an sio driver which is part of many distributions. However, MPSSE (for SPI) will require you to load our D2xx drivers which can be obtained from our D2xx drivers page. We have these for various Linux platforms but it will also depend if the Kinetis uses one of our supported processor types,

Best Regards, FTDI Community

Pages: [1] 2 3 ... 45