cutiepi-io / cutiepi-board Goto Github PK

@penk perhaps i overlooked, what type of hdd or sdd are supported? how much gb is supported?

I might've missed it somewhere, but I think there is no info on the LCD and the battery part numbers and/or links?

If I understand correctly the internal Compute Module eMMC is not accessible, because it is connected to same bus as SD card. It could be solved by connecting sd card to USB bus.

Is 8" enough? It would be nice to be able connect bigger screen instead.

Is there some issues list? Similar to the this page https://wiki.pine64.org/wiki/PinePhone_v1.1_-_Braveheart#Known_issues

The display and CM does support TE line, have u tested to use it?

So while playing with camera, the gyro is not accessible?

How does the built in display connect to the mainboard?

Does the CutiePi support HDMI Input (or just HDMI OUTPUT)?

The use-case I have in mind:
Using CutiePie as a regular tablet (especially for reading books) for the most part with a full linux environment. But when needed, be able to plug in a Samsung phone that supports Samsung Dex to access better supported proprietary apps (Office Apps: Word, Powerpoint, etc; Adobe Apps: Photoshop Express, Acrobat, etc).

I.E.: can the CutiePi be used as a portable monitor?

In my opinion lora is very important addons

Hi,

I doubt that I'm first one who think about keyboard module transformer to have nice UPMC-like this one with Quad cores 8GB of RAM and first class linux support.

Is there wired keyboard module in a wild?

Thanks,
B.

I love this project, but it's a stretch to claim it's open-source if closed-source software is required to modify the design files. Please consider switching to KiCAD, etc., or at least post a KiCAD-friendly version of the source. Thanks!

Most of us don't have Cadence software, if possible export the files to a universal file so everyone can make use of it. also if possible a separate library file that includes all the parts used in the design.
thanks.

The MP2636GR can not full fill requirement of CM4.
CM4 works between 4.75 to 5.25 V.
If the USB C is plugged in then pulled out.
The MP2636GR can first start the boost of battery when the voltage dropped to battery voltage + 300mv.
This will cause the CM4 shut down.
we found a temporary solution for this, change the R3092 to 3k, it will solve the problem.
But the resistor must be very precision. above 3.3k or below 2.7k will not solve this problem.
We afraid that the tk of resistor will also impact the reliability of the pad.
But we didn't have further test.

On the schematics the HDMI interface looks like the CM3+ HDMI interface. The CM4 has a simplified interface, see the CM4IO board. You no longer need the ESD device as that is built into the CM4 also you no longer need the hotplug is inversion.

I like Fomu or other good project fpga.
Is possible add in second version small fpga processor directly on board? Or in version 1 more STM processor for kernel.

Many programs need small power. Many emulators working on fpga and RISC-V, DOS, Commodore

Hello;

Generally laptops and mobiles will charge themselves whenever they are plugged in to an external power source.

However, I'd like to use a Cutiepi during travel, and well beyond the 5 hour window.
I figure I can use power banks for this, -if- there is a mode available in which the device will not auto-charge.
Continually charging one battery from other batteries would be a waste of energy and available work time.

Is there a physical switch between auto-charging and no-charging, ie merely powering the Cutiepi from the external power source?
Or can it be done through software?

In the latest schematic (v2.3) the !RST pin of the display LCD_RST is connected to GPIO6 of the CM4.

looking at the dt-overlay source cutiepi-panel-overlay.dts, I could not find where the GPIO6 as !RST is declared.

the only part where I can see something related to the display rst is this:

reset-gpios = <&gpio 20 0>;

but it looks like &gpio is the number 12, used for backlight control

fragment@1 {
        target = <&gpio>;
        __overlay__ {
            pwm_pins: pwm_pins {
                brcm,pins = <12>;
                brcm,function = <4>; // ALT0
            };
        };
    };

could you please clarify?