PocketBeagle U-Boot Overlays [naming???]

So i'm working on adding support for a few Overlays (taking advantage
of the CLICK interface)..

What do you guys think of this naming:

Option A/B: (there's no A or B on the board)

PB-A-RTC-6-CLICK-00A0.dtbo
PB-B-RTC-6-CLICK-00A0.dtbo

Use the interface names:

PB-U4-I2C1-SPI0-RTC-6-CLICK-00A0.dtbo
PB-U2-I2C2-SPI1-RTC-6-CLICK-00A0.dtbo

Option U/M (aka U=USB, M=MicroSD) because Click "fits" over that...

PB-U-RTC-6-CLICK-00A0.dtbo
PB-M-RTC-6-CLICK-00A0.dtbo

I personally like the U/M option.. as it the easiest to explain to new
users (or is it?).

Thoughs???

Regards,

Ps, if we assume "config-pin" we can make these much simplier:

https://github.com/RobertCNelson/bb.org-overlays/commit/aa5491da3444e3f33dc128ab8650312b32ded0f1

root@beaglebone:~# dmesg | grep rtc
[ 1.836679] rtc-ds1307 1-006f: rtc core: registered mcp7941x as rtc0
[ 1.836716] rtc-ds1307 1-006f: 64 bytes nvram
[ 1.839208] omap_rtc 44e3e000.rtc: already running
[ 1.839793] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc1
[ 1.950076] PM: bootloader does not support rtc-only!
[ 1.952034] rtc-ds1307 1-006f: setting system clock to 2017-09-26
17:00:18 UTC (1506445218)

Regards,

The interface names seem much more self explanatory.
The U/M option is workable.

— Graham

They list 381 varients:

https://shop.mikroe.com/click

So 381 * 2 dtb overlays..

99% of them use one interface, SPI/I2C/UART

So if we had to use the interface name, i'd probably simplify it to just:

PB-I2C1-RTC-6-CLICK-00A0.dtbo
PB-I2C2-RTC-6-CLICK-00A0.dtbo

Maybe that'll be good enough to help users know which side to plug in?

Regards,

Looks good to me.

Just out of curiosity though. What’s with the sudden interest with Mikrobus click devices ? Just wondering, as we used one of their boards in a design about a year ago.

Just out of curiosity though. What’s with the sudden interest with Mikrobus click devices ? Just wondering, as we used one of their boards in a design about a year ago.

When we looked at prototypes, we just had some laying around and it looked like it would be easy to adjust the footprint to allow for two of those boards. The support isn’t official or anything as of now, just good fortune.

Your naming proposal seems appropriate.

The mikro Click boards seem to be good for experimenting with one new part or function.
Microchip is supporting them on their new “Curiosity” series dev boards, too.

Great for learning to program an I2C, SPI or UART interface.

Easy to layout unique little PCBs fitting that footprint. I have already done that for a unique ADC and a 6 pin console serial port adapter.

Where it starts to fall apart is when you want to use more than one or two “Click” boards worth of functionality, although mikro does have a separate four-up universal click board motherboard.

— Graham

I've started listing working boards here:

https://github.com/beagleboard/pocketbeagle/wiki/mikroBus™-Click-Boards

I've got a spi and i2c example working.. So it should be easy for
others to add additional boards. :wink:

Regards,

Will the same Ethernet overlay work for both the ETH Click and the ETH-WIZ Click?

Since the 10/100 Mb Ethernet (ETH WIZ) Click board is $19, and the 10 Mb only ETH Click board is $24, I bought the 10/100 ETH WIZ click board.

— Graham

Will the same Ethernet overlay work for both the ETH Click and the ETH-WIZ
Click?

Nope different driver..

Since the 10/100 Mb Ethernet (ETH WIZ) Click board is $19, and the 10 Mb
only ETH Click board is $24, I bought the 10/100 ETH WIZ click board.

I also have the ETH Wiz, however it's driver went mainline in v4.7.x.
I need to backport it..

Regards,