Will the PineTav-V use the same chip as the Star64 or a different chip?

Mike

Hi everyone,

(I hope I'm posting in the right place. If not, please let me know.)

I have been using PineTime since 2021 and I really like it. I'm absolutely a FOSS-guy who welcomes any open/community-based projects, such as PineTime which is a fully open (hardware and software) and long overdue product in the smartwatch market.

I'm studying Computer Engineering at university. Many of us design a high-level application (Java, Python etc.) or a webpage or something AI related stuff. However, I'm rather a hardware (IoT/embedded systems) -oriented person, and that's why many people think i'm crazy when I say: "I loved my Assembly programming course"

To be honest, when I bought my first PineTime, I ordered a twin pack (sealed and devkit), because I knew that I would like to modify/hack/develop my watch in the future. And now it seems like a good idea to deal with PineTime because it perfectly fits my studies and who knows... maybe that could be even a great theme for my thesis. Moreover, it would be a great adventure (doing it for fun).

I'm planning to create a new (very basic) firmware from scratch. I mean that would be an independent and separate project from InfiniTime / Wasp-OS or other relevant PineTime related firmwares, although it would rely on some third party libraries (such as LVGL or FreeRTOS) and it would use existing projects (mostly InfiniTime) as a reference.


Initial (essential) objectives:

• display time without any smart capabilities (e.g. Bluetooth synchronization)
  

• Bluetooth implementation
  
• Heart rate measuring
  
• Step counting
  
• Built-in apps
  
• ...
  

Just bought a board (in India), have tried various images on pine site and different power supplies and SD cards the board always gets stuck on

U-Boot SPL 2022.04 (Mar 01 2023 - 00:14:33 +00000)
DRAM:

it never goes past DRAM:

the date after SPL changes with different images but it's stuck on DRAM:

once in a while it give this message once , restarts and gets stuck on DRAM again:

DRAM: This DRAM setup is currently not supported.

From looking at the specification, it seems the StarFive JH7110 is weaker than the Rockchip RK3399 but has more L2 cache. In performance I imagine the star64 will be slightly stronger than a RK3399 based device with its a72 cores disabled, in the case of pine64 hardware, only better because of the 8gb of ram?

Comparing GPUs, weaker but support for newer standards?

Do you agree? Difficult to benchmark, perhaps need the 4gb star and 4gb rock to go head to head.

What OS is primarily being worked on for the PineTab-V?  Also, is there a channel for RISC-V development?  I would be interested in helping.

Mike

this is little bit offtopic of pine forums, but i think it interests some users. other kind of 2fa/mfa.

because of possible privacy issues, data collection and locking to close platforms, like google play and apple store, i don't usually like 2fa or mfa. two-factor-authentication or multi-factor-authentication is additional required policy for many services to getting in.

i found by coincidence a reasonable alternative, which can be used for 2fa/mfa systems. essentially, it has no privacy or data collection issues (assuming of usage). it is totp https://en.wikipedia.org/wiki/Time-based...e_password . it is based on time and correct timezone.

i initiated this on some services already, but i don't name those here, because of advertising. quite often, it is called an "authenticator app".

also hardware based totp devices are available, but might be cumbersome to be activated for service.

in debian, there is a package "oathtool". which can used by following, note -b is for base32.

Hello,

I am new to Linux (except Ubuntu) and to this forum; my PinePhone is my first "smart" phone (at age 70!) so my questions will likely be elementary.  Thanks for your patience.

My problem is that the virtual keys don't produce audible tones when touched so that I can't use it for automated phone systems ("Press 1 Now" for example).  I've looked everywhere I can think of in Settings including Sound, Tweaks, Mobile Settings and Keyboard to no avail.

Thanks in advance.

p.s. The application is 'Calls'.

Highlights for March:
- move from lightdm to systemd based autologin
- fixes in ngfd and volume settings slider

http://nemomobile.net/pages/nemomobile-in-march-2023/

This post is mainly to share my tests result, but I have two questions:

- Did someone managed to boot from this SSD? Boot from Intel 660p 2 TB works fine but not this one?

- I noticed that my tests on the Intel 660p 2 TB are slower than before any idea why?
I am using Armbian with linux kernel 5.15.93-rockchip64 #23.02.2, we might get better results on linux kernel v4?

Note: The RP64 has a PCIe NVMe v2.0 x4 (not a v3.0) the speed is limited and not representative of the SSD real performance.


WRITE
sync; dd if=/dev/zero of=tempfile bs=512 count=1024 oflag=dsync; sync; rm tempfile
524288 bytes (524 kB, 512 KiB) copied, 0.720266 s, 728 kB/s

sync; dd if=/dev/zero of=tempfile bs=1M count=1024; sync; rm tempfile
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 3.60083 s, 298 MB/s

sync; dd if=/dev/zero of=tempfile bs=1G count=4 oflag=dsync; sync
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 15.6034 s, 275 MB/s

READ
dd if=tempfile of=/dev/null bs=512 count=2048
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0285999 s, 36.7 MB/s
dd if=tempfile of=/dev/null bs=1M count=1024
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 2.00752 s, 535 MB/s
dd if=tempfile of=/dev/null bs=2M count=2048
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 7.23786 s, 593 MB/s


[b]sync; sudo sysctl vm.drop_caches=3
hdparm -tT --direct /dev/nvme0n1[/b]
Timing O_DIRECT cached reads:   1096 MB in  2.00 seconds = 548.08 MB/sec
Timing O_DIRECT disk reads: 1714 MB in  3.00 seconds = 570.76 MB/sec

sync; sudo sysctl vm.drop_caches=3
hdparm -Tt /dev/nvme0n1


Timing cached reads:   2472 MB in  2.00 seconds = 1235.97 MB/sec
Timing buffered disk reads: 1484 MB in  3.00 seconds = 494.27 MB/sec

I have playing around with gokrazy, a unikernal project for the RPi, and very interested to see if such a project is feasible with your new upcoming Star64 Risc-V SBC.  I have some assembly code that initialises the Pi, and first step would be porting this over.  Is the Star64 documented well enough for such a project, I know that the Pi benefits from being around for a long time.  I can see 4+1 cores? (JH7110 has 6 no?) and already keen to find some documentation in preparation for your launch.