BRT Community

Hello,

The core issue here relates to the size limitation of RAM_G.

Rudolph has covered the main options, scaling down the image or using the ASTC image type.

The encoding process for ASTC is quite slow, compared to decoding.
There is a real-time encoder called ASTCRT, (https://github.com/daoo/astcrt). You could try encoding the JPEG stream to ASTC stream on the fly. I may suggest they can use block size 6x6 and veryfast option while encoding.

Best Regards,
BRT Community

Hello,

The IC designers have confirmed that this is a limitation of the BT815, and can only be resolved in the next iteration of the silicon.

Best Regards,
FTDI Community

Hello Chris,

This could be an ESD issue if you are only experiencing this issue whilst not at your desk.

Is it the Cleo50 or Cleo35 modules you are using?

Best Regards,
BRT Community

Hello,

There is nothing built into I2C to do this, normally slave devices will have some externals pins that can be set to 0 or 1 to toggle a couple of the address bits to avoid this issue. There are some manufacturers that have 4 or 5 part numbers for a part, the only difference being its I2C address.

Best Regards,
BRT Community

Hello Juergen,

We're currently investigating this and will continue our discussion by email at the moment and we'll post an update here once we have closed the issue for other users to refer to in future. We'll send you another email in case you missed our first reply.

Best Regards,
BRT Community

Hello,

Yes multiple I2C devices can be connected to an I2C master.

Actually there are two on the board that we use in our software examples, U6 and U11.

The master generates the clock and initiates communication with the slaves with a 7-bit address.

You can find more information on I2C protocol online.

I also need to comment that there have been additional changes to the MM900EV1B over the MM900EV1A on top of RevC. However these changes shouldn't affect you. I'm looking to get the schematics up on our website. They can be found on our FTP site for now:

MM900EV1B Schematic.pdf

Best Regards,
BRT Community

Hello,

Yes the only difference is the IC which contains FT900 RevC.
We are working to get this corrected on the website.

The I2C1_SDA and I2C1_SCL signals are available via CN3 (GPIO47 and GPIO46 respectively).
I2C bus external pullups are also present on the hardware.

Many I2C devices (127) can be connected to the same I2C master.

Best Regards,
BRT Community

Hello,

We already have software examples which access U6. Full Part number is 24AA02E48T.
This EEPROM stores a permanently write-protected MAC address in upper half of memory array.

/* Set up I2C */
i2cm_init(I2CM_NORMAL_SPEED, 10000);

/* Enable the I2C device... */
sys_enable(sys_device_i2c_master);

/* Setup I2C channel 0 pins */
    /* Use sys_i2c_swop(0) to activate. */
    gpio_function(44, pad_i2c0_scl); /* I2C0_SCL */
    gpio_function(45, pad_i2c0_sda); /* I2C0_SDA */

    /* Setup I2C channel 1 pins for EEPROM */
    /* Use sys_i2c_swop(1) to activate. */
    gpio_function(46, pad_i2c1_scl); /* I2C1_SCL */
    gpio_function(47, pad_i2c1_sda); /* I2C1_SDA */

/* Set the I2C Master pins to channel 1 */
sys_i2c_swop(1);

//read MAC address and other network parameters.
my_netif.hwaddr_len = 6;
i2c_status = ee_read(NET_EEPROM_OFFSET_MACADDRESS, &my_netif.hwaddr[0], 6);
i2c_status = ee_read(0, (uint8_t *)&er, sizeof(struct eeprom_net_config));

Note: NET_EEPROM_OFFSET_MACADDRESS = 0xFA

See FT90x Ethernet Video Bridge for the source code.

Higher resolution schematics can be found here:

https://www.ftdichip.com/Support/Documents/Schematics.htm

If you have any other questions you can send us an email.

Best Regards,
BRT Community

Hello Filippo,

The 2nd bullet point was already confirmed by us.

Let us look into the first point.

If there are any code errors, we will update in the next toolchain release.

In any case, the source code is provided so you can make any changes.

Best Regards,
BRT Community

Hello,

It would be worth trying the non-compressed versions of your font first of all to check if this works when you load two copies of the same font. Also, does your 7-segment font work if you load only one copy / one size ?

Could you also send a copy of your font files (both pre and post conversion) to us at our support address? If you could send an email initially to support.emea@brtchip.com with no attachment then we can get back to you.

We'll also post any updates here once we have investigated for future reference.

Best Regards,
BRT Community

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

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

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

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

    /* 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

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