BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - BRT Community

Pages: 1 ... 48 49 [50]
736
Discussion - EVE / Re: ASTC viewer?
« on: February 12, 2019, 11:31:34 AM »
Hi Rudolph,

Thanks for your feedback. We'll discuss these points with our development team and get back to you on these.

Best Regards, BRT Community

737
Discussion - Cleo / Re: CleO50 internal RTC
« on: February 08, 2019, 03:39:43 PM »
Hello,

Unfortunately the on-board RTC API is not currently available. You can connect an external RTC via the I2C lines of the Click board connectors however.

We have some software examples within the Projects section of the help file which use the external RTC and which might be a useful reference. One example would be the 'Project 06 - A Traditional Analog Clock' which uses an external RTC.

Best Regards,
BRT Community

738
Discussion - EVE / Re: BT815: Problem with displaying custom fonts
« on: February 06, 2019, 09:37:15 AM »
Hello,

Would it be possible for you to email in to our support address: support.emea@brtchip.com
Please include any applicable code and the converted font files from EAB.

Best Regards,
BRT Community

739
Discussion - MCU / Re: FT90x ADC & DAC section quite undocumented
« on: January 30, 2019, 04:05:37 PM »
Hello, great thanks for the feedback. I'll look into getting this added to the documentation.

As for the issue in DAC, I looked into this.

In single shot mode, single conversion works with the following excerpts from DAC Example 1

Code: [Select]
    /* Enable the DAC device... */
    sys_enable(sys_device_dac0);

    /* Make GPIO14 function as DAC0... */
    gpio_function(14, pad_dac0); /* DAC0 */

    /* Set the DAC to single shot mode */
    dac_mode(0, dac_mode_single);

    //dac_start(0);  ------->> this seems to have started the single data conversion

    dac_write(0, 1000);


dac_write() API writes data to the data register and performs start operation.
So a prior dac_start() is not needed.

Best Regards,
BRT Community

740
Hi,

We were not able to reproduce the issue here. If you have a small example project which shows the issue, could you send it in to our support address and we can investigate further? You can contact us at support.emea@brtchip.com

Best Regards,
BRT Community

741
Discussion - MCU / Re: FT90x ADC & DAC section quite undocumented
« on: January 28, 2019, 04:40:55 PM »

742
Discussion - EVE / Re: BT81x and VERTEX2F
« on: January 25, 2019, 02:28:23 PM »
Hello,

Thank you for your suggestion, it is an interesting approach and one which I will pass on to the development team.

Best Regards,
BRT Community

743
Hello,

Welcome to the forum,

We will try to reproduce this issue and will report back soon,

Best Regards, BRT Community

744
Discussion - MCU / Re: FT90x ADC & DAC section quite undocumented
« on: January 24, 2019, 12:05:17 PM »
Hello,

Rev B has actually recently been replaced by Rev C:

PCN BRT 005
BRT AN 019 Migration Guide Moving from FT90x Revision B to FT90x Revision C

The ADC in FT90x Revision C is similar to the ADC in FT90x Revision B with some improvements as
stated below.
Change in FT90x Revision C:
  • The FIFO Data Count issue, as stated in TN_159 FT90x Errata Technical Note, section 4.3,
    has been fixed. Counts of 0x7E and 0x7F now appear correctly, and 0xFF indicates the
    FIFO is empty.
  • A bit has been added to select the size of the ADC samples: either 10 bits or 8 bits.
  • A bit has been added to select the ADC clock speed: 12.5 MHz or 6.25 MHz.
  • The internal Op-amp has been removed.

The mm900ev1b can be used to evaluate RevC silicon.

All available information on the ADC can be found at the product page:

https://brtchip.com/ft900/

If you have any other questions you can email our Tech Support at support.emea@brtchip.com.

Best Regards,
BRT Community

745
Discussion - EVE / Re: BT815 Camera with STM32
« on: January 23, 2019, 11:46:08 AM »
Hi Gokhan,

Our camera examples are currently for the FT90x series MCUs and so may not work directly with other MCUs as their camera interface may be different. The EVE part of the code can certainly be ported over however. We have an STM32 example for the FT81x which you could use as a starting point.

We have an example below of camera to FT81x which could be ported to other MCUs but the camera part of the code would require some modification.
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/MCU/BRT_AN_018-FT90x-Camera-to-EVE.pdf

The method of displaying depends on the camera and image format. In the demo above the frames are sent to EVE as a series of images as they are coming in real time from the camera and so the MCU would provide any buffering required.

Best Regards, BRT Community




746
Discussion - Cleo / Re: CleO file write append to new line
« on: January 22, 2019, 02:26:57 PM »
Hello,

Thanks for you solution!

Best Regards,
BRT Community

747
Discussion - Cleo / Re: CleO External Flash Fail
« on: December 16, 2018, 09:40:12 PM »
Hi Chris,

Sorry to hear of the problem, we'll need to check on this.

Is there anything which seems to trigger the issue to begin happening on the boards (such as changing the contents of the eflash to add images or connecting or configuring differently)?

Best Regards, BRT Community

748
General Discussion / Re: Splash screen change
« on: December 12, 2018, 03:34:51 PM »
Hello,

Unfortunately there has been no progress on removing the CleO image from the splash screen.
I will post here when there if there is any update.

Best Regards,
BRT Community

Pages: 1 ... 48 49 [50]