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.

Topics - NW27

Pages: [1]
1
Discussion - Software / FT81x and available free GRAM
« on: June 26, 2018, 11:25:49 PM »
Hi,
How can I determine how much available free GRAM I have in the FT81x GPU?
Is there a call to the GPU that I can perform that shows me some stats?

Thanks,
Neil.

2
Discussion - Software / FT900 RTC Interrupt - Help needed
« on: June 25, 2018, 07:32:28 AM »
Hi,

I have the RTC oscillator ticking over. So the RTC_start, RTC_Read, RTC_Write and RTC_Stop seem to be working.
It seems to be adding about 36 counts per second. Is this correct? This seems to be a bit of a strange value. How do you set a divisor for this?

Ultimately, what I would like to do is have a RTC interrupt that happens every second.

I am using the MikroC compiler from Mikro Electronica.
I have the RTC interrupt vector (void RTC_ISR() iv IVT_RTC_IRQ ics ICS_AUTO ) pointing to my RTC Time updating code but basically the system just locks up when I enable the interrupt
Using     RTC_IEN_bit = 1 ;
RTC_CCR looks like 0x00 00 00 05.

Do I need to do something at the end of the interrupt ie clear a flag etc?

Thanks,
Neil.

Code: [Select]
tByte rtc_start(void)
{
//    RTC->RTC_CCR |= MASK_RTC_CCR_EN;
    RTC_EN_bit = 1 ;
    return 0;
}


tByte rtc_stop(void)
{
//    RTC->RTC_CCR &= ~MASK_RTC_CCR_EN;
    RTC_EN_bit = 0 ;
    return 0;
}


tByte rtc_write(unsigned long val)
{
//    RTC->RTC_CLR = val;
    RTC_CLR = val;
    return 0;
}

tByte rtc_read(unsigned long *val)
{
//    *val = RTC->RTC_CCVR;
    *val = RTC_CCVR;
    return 0;
}


tByte rtc_init(rtc_wrap_t wrap)
{
    tByte iRet = 0;
    if (wrap > rtc_wrap_enabled)
    {
        iRet = -1;
    }

    if (iRet == 0)
    {
        rtc_write(0UL);

        switch(wrap)
        {
            case rtc_wrap_disabled: RTC_CCR |= RTC_WEN; break ;
            case rtc_wrap_enabled: RTC_CCR &= ~RTC_WEN; break ;
            default: break;
        }
    }

    RTC_IEN_bit = 1 ;
    return iRet;
}


void RTC_ISR() iv IVT_RTC_IRQ ics ICS_AUTO {
  tbyte a ;
  if (++RTClock.second==60)        //keep track of time, date, month, and year
  {
    RTClock.second=0;
    if (++RTClock.minute==60)
    {
      RTClock.minute=0;
      if (++RTClock.hour==24)
      {
        RTClock.hour=0;
        if (++RTClock.dow==7) RTClock.dow= SUN ;
        if (++RTClock.date==32)
        {

Etc etc

3
Discussion - Software / Display issues with Special character
« on: April 17, 2018, 06:17:43 AM »
Hi,
I'm using the MikroC compiler to program a FT90x and FT812 display.
When I write the following to the display "°C", the display severely breaks up with missing text/boxes and squiggly lines displayed. The issue is the "°" degree symbol. If I leave this out, the display works perfectly. If I write "DegC" it works perfectly (point being that it is not a string size issue).
Is there an issue with the FT812 displaying special characters?

Thanks,
Neil.

P.S. Does every post have to be approved by a moderator?

4
Discussion - Software / Camera software for FT90x connected to a FT81x
« on: April 09, 2018, 11:36:01 AM »
Hi,
I have purchased the FT90x C compiler  https://www.mikroe.com/mikroc-ft90x from MikroeElektronica along with a 7" display MIKROE-2290 https://www.mikroe.com/mikromedia-hmi-70-cap. The display has a Riverdi 800x480px with a FT813 EVE controller.

My initial goal is to connect a OV7670 camera to the FT900Q micro and display the live video image directly onto the display via the FT813 EVE controller.

The next goal is to then connect a Analog Devices ADV7280A in place of the OV7670 camera. The ADV7280A is a PAL (800*600) 4 analogue input  Video Decoder that simulates a parallel camera. The software will then select the required camera input and display the live feed.

Would you be able to give some assistance with the initial goal of interfacing the camera and feeding the live image directly to the display.
Any generic C code examples of configuring the FT900 and feeding the (BMP or JPG) image to the FT81x would be great.

Thank you,
Neil.


Pages: [1]