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 - hdc

Pages: [1]
1
Discussion - MCU / Re: MM900EV1B dimensions - relative board X/Y of J2 from CN3
« on: December 23, 2020, 07:46:33 PM »
Following up to thank you for the support here and by e-mail.

After clarifying my question we ended up using:

X = 33.005 mm
Y = 74.26  mm

as the position of the pin center for J2-1 relative to CN3-1. 

These (unofficial) dimensions worked well for us.

Thanks again,
David

2
Discussion - MCU / Re: MM900EV1B dimensions - relative board X/Y of J2 from CN3
« on: August 26, 2020, 08:58:40 PM »
Thanks very much.  I'll follow-up by e-mail;  having a step model would be useful as well. (update - e-mailed the support.us address.)

David

3
Discussion - MCU / MM900EV1B dimensions - relative board X/Y of J2 from CN3
« on: August 25, 2020, 05:57:28 AM »
Hello all - hope everyone is doing well,

On the MM900EV1B board, what is the position of the

   J2 connector (dual-entry SPI master)

relative to the

   CN3 connector (40-pin external I/O) ?

For example, J2 pin 1 relative to CN3 pin 1 or 27 or each
relative to the origin marker on page 6 of the MM900EVxB
Datasheet v1.0.

Thanks in advance.

4
Discussion - MCU / Re: MM900EVxB I2C eeprom question / datasheet readability
« on: March 09, 2019, 06:18:09 AM »
Thanks for the update on the schematic.

Appreciate the support and apologies for not being clearer. My question was specifically about I2C eeproms on the same bus that share the same device address (0x1010) and one of them has no address pins and appears to listen only for the device address 0x1010 rather than being hardcoded to a particular full address. It seems like this would not be an effective configuration because both eeproms would respond but that was what I was trying to confirm/understand.

Rather than take up more of your time will take your suggestion and look elsewhere if we need more info on this.

Thanks again,
David
HDC

5
Discussion - MCU / Re: MM900EVxB I2C eeprom question / datasheet readability
« on: March 05, 2019, 07:54:22 PM »
> 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.

I'm not an I2C expert by any means.  Are you saying that it is possible to add a second EEPROM to I2C1 on the MM900EV1B?

The 24C1024 we have is connected to I2C1 via CN3 pins 25 (GPIO46) and 26 (GPIO47). Added 2 jumpers with the 24C1024 for setting A1 and A2 of the device address for the 24C1024; these can be tied to either pin 23 3V3 or pin 24 GND.  The code to set up the I2C master is essentially what you provided earlier but includes the #ifdef obviously. That is set to channel 1.

Appreciate the help with this and thank-you for the information about the A vs B board difference.

David
HDC

6
Discussion - MCU / Re: MM900EVxB I2C eeprom question / datasheet readability
« on: February 27, 2019, 08:49:10 PM »
Thanks very much for the part number and link to the schematics.

I found the schematic for the MM900EV1A board (perfectly readable - thank-you!) but don't see a schematic for the MM900EV1B version of the board; is the only difference the FT900Q-C?

Thanks for the code reference but believe our code is working correctly; the design requires a larger eeprom. An aside, the 24C1024 we're using with the prototype requires 2-byte addressing. I had referred to the OV5640 code in the 2.5.0 Toolchain example "USBD Example UVC Webcam" for the registers/flow with 2-byte addressing.

The primary reason for switching to the MM900EV1B board was to take advantage of the built-in USB host port to help move our prototyping along quickly (no ethernet port in this design.) I simply wasn't paying enough attention to the other board differences like U6.

In the interests of time I have since removed U6 solving my immediate problem but again, interested to know if I'm overlooking some other way to add a second I2C epprom with the EV1B.

Thanks again,
David
HDC


7
Discussion - MCU / MM900EVxB I2C eeprom question / datasheet readability
« on: February 22, 2019, 07:23:53 PM »
Greetings,

I'm attempting to port 24C1024 I2C eeprom code to the MM900EV1B (FT900Q rev C) board from the LITE board (rev B) but after getting unexpected read behavior realized that U6 is on the I2C1 bus but appears to not have any address pins.  The part number is largely unreadable on page 12 of BRT_00021 (MM900EVxB Datasheet Version 1.0) but might be a 24AA02.  Microchip's docs for this part number don't come right out with it while ON Semi's says "In  contrast  to  the  CAT24C01/24C02,  the  CAT24AA01/24AA02 have  no  external  address  pins,  and  are  therefore  suitable  in applications that require a single CAT24AA01/02 on the I2C bus."

Questions:
1) is U6 a 24AA02 part (and what is it's full part number please) used on the MM900EVxB boards
2) is there some way to use an additional I2C EEPROM with any of the MM900EVxB boards that I'm overlooking?

Feedback:
1) I notice a number of the FTDI and BridgeTek docs appear to have overly compressed images for schematics in particular.  Is it possible to get higher-resolution copies and if so how or if not would you please consider settings which improve the readability.

Thanks in advance,
David
HDC

Pages: [1]