Support and General Use > Hardware

HiBy R1

<< < (6/7) > >>

Milardo:

--- Quote from: 7o9 on June 13, 2025, 02:26:17 PM ---In firmware/export/config/hibyr1.h I have set HAVE_DUMMY_CODEC.

If you enable HAVE_HIBY_R1_LINUX_CODEC instead, you would have to implement firmware/drivers/audio/hibylinux_codec.c.

However, ALSA shows no devices when you run ‘amixer’ or ‘amixer contents’ like described here for the AGPtEK Rocker device: https://www.rockbox.org/wiki/AgptekRocker.html

This part seems to be different in this ‘X1600E’ generation of HibyOS.

--- End quote ---

Does this help in any way? Specifically, (google translate)

https://www.ingenic.com.cn/news-detail/nid-338.html


     7. Updating the Audio driver

         a. Deprecate amixer and configure the data path in the form specified in the board header file

     7. Update Audio Driver

         a. Abandon amixer and configure the data path in the board header file

vitt13:

--- Quote from: Milardo on June 21, 2025, 02:47:41 AM ---Does this help in any way? Specifically, (google translate)
--- End quote ---
Yes, at least You found the way to access their FTP with dev resources. pan.baidu link -> M300-> 01_SW -> 08_M300_kernel... leads to ReadMe.md.txt
and under last "* Download USBCloner" You may find link to Ingenic FTP.
And this is kernel source code path on FTP /DevSupport/X1600/01_SW/08_kernel5.10_X1600-sdk_v6.0-20250410/01_ingenic-linux-kernel5.10-x1600-v6.0-20250410

Milardo:

--- Quote from: 7o9 on June 16, 2025, 11:24:03 AM ---Yes, through adb.

You can turn on adb in the boot menu and then connect over usb to play around.

It does not matter if you run Rockbox or the HiBy player after that.

--- End quote ---


Did this help in any way? Specifically, (google translate)

https://www.ingenic.com.cn/news-detail/nid-338.html


     7. Updating the Audio driver

         a. Deprecate amixer and configure the data path in the form specified in the board header file

     7. Update Audio Driver

         a. Abandon amixer and configure the data path in the board header file

kae0:
Sadly i also haven't been successful at repacking the upt files, your genisoimage turns out to be the closest with it's binary content, though I noticed the structure of rootfs changing which could totally answer our question of why it didn't boot.

Changing settings in genisoimage to get the untouched rootfs structure didn't work in a timely manner, so i used xorriso  ;D

xorriso -as mkisofs -volid 'CDROM' -JRU -joliet-long -o $workingdir_out/$updatefile $workingdir_out/image_contents/

This one didn't modify rootfs, and from what i have seen the beginning of xImage is also in tact, so i believe it could work.

I have to wait for Tempotec to drop an update to test doe

Also while i was trying to fix my mistakenly wiped mtd2 partition, i've found Ingenic ftp server and credentials, cuz they seem to change that thing once in a while.

ftp.ingenic.com.cn
szingenic
hq7Wy0gws


I've noticed Tempotec Variations* V1's firmware is based mostly on Hiby R1 firmware, in my case amixer shows:

Simple mixer control 'DOP_EN',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'Digital Filter',0
  Capabilities: volume volume-joined
  Playback channels: Mono
  Capture channels: Mono
  Limits: 0 - 4
  Mono: 0 [0%]
Simple mixer control 'Left',0
  Capabilities: pvolume pvolume-joined
  Playback channels: Mono
  Limits: Playback 0 - 255
  Mono: Playback 0 [0%]
Simple mixer control 'Mute Output',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'NOS_EN',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'Right',0
  Capabilities: pvolume pvolume-joined
  Playback channels: Mono
  Limits: Playback 0 - 255
  Mono: Playback 0 [0%]
Simple mixer control 'Soft Mute',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]

7o9:
You tried to repack the .upt file without making changes and that failed? That suggests the problem is with the iso generation indeed. I still have no idea why.

Tempotec confuses me. Is this V1 a new device (using the X1600) or an old one (using the X1000E)? There was a V1 in 2019 already.

I thought all X1600 devices use this ‘new’ way without amixer.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version