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

Pages: [1] 2 3 ... 5
1
hi
I am developing my own bootloader, supporting
- C1000
- C3000

yesterday I prepared an SD card
- PC partition FAT16
- mkfs.fat

then I copied
- update.sh
- zImage <----- my application

I followed the instruction to enter the Sharp Menu.
As result:
- C1000 perfectly flashed, now it boots my bootloader
- C3000 says it can't update anything "because the microdrive is missing". No option.

I removed the microdrive because it was faulty, the C3K is designed to boot completely from the SD card. I still need to find and buy a replacement for the internal MD.

It's absurd that update.sh refuses to flash because the microdrive is missing ...

Any workarounds?

2
I know there is a JTAG interface inside the PXA270 SoC.
I don't know if it is connected to a PDA connector.

Any doc?

3
In particular, I'm trying to figure out what problems there are with
  • Flash on Zaurus -> can I erase everything and use the Zaurus Flash (C1K, C3K) for my stuff?
  • Suspend/Resume
  • PowerCharge
  • PowerManagement
  • TouchScreen -> too noisy on a SDL application I wrote to take notes -> should I put a software filter into its kernel module?!?
  • USB, why is it so slow?!? I get ~1Mbyte/sec on a 10/100Mbps USB-NIC ---> it's not USB2, but rather USB1?!?

I also found a Russian forum that was about Gentoo/Zaurus around 2009.
I see patches for kernels 2.6.22 and later.

4
p.s.
wrote a nice tool to automagically get stuff from an internet url, even recursively

Code: [Select]
macmini2-intel irc # echo "https://logs.nslu2-linux.org/livelogs/kexecboot/" > url
macmini2-intel irc # myNET-get-files-from-url url
list_preparing1, getting index.html ... success
preparing /list ... done
downloading [kexecboot_20110601.txt] ... success
downloading [kexecboot_20110602.txt] ... success
downloading [kexecboot_20110603.txt] ... success
downloading [kexecboot_20110604.txt] ... success
downloading [kexecboot_20110605.txt] ... success
downloading [kexecboot_20110606.txt] ... success
downloading [kexecboot_20110607.txt] ... success
downloading [kexecboot_20110608.txt] ... success
downloading [kexecboot_20110609.txt] ... success
downloading [kexecboot_20110610.txt] ... success
downloading [kexecboot_20110611.txt] ... success
downloading [kexecboot_20110612.txt] ... success
downloading [kexecboot_20110613.txt] ... success
downloading [kexecboot_20110614.txt] ... success
downloading [kexecboot_20110615.txt] ... success
downloading [kexecboot_20110616.txt] ... success
downloading [kexecboot_20110617.txt] ... success
downloading [kexecboot_20110618.txt] ... success
downloading [kexecboot_20110619.txt] ... success

I take this opportunity to test it  ;D

5
thanks!

I am working on a low level bootloader, plus kernel stuff.
Need info, I can't find around.

I will wget and search into logs

6
Zaurus - Void Linux support / who is working on the Zaurus Kernel?
« on: May 12, 2025, 12:50:37 pm »
hi
is there a mailing list or something to discuss the kernel development? patch? etc
is there still interest?

let me know.
D.

7
HI
I need it for the development of Zaurus C3K
Let me know if you have one for sale.
Thanks

8
Zaurus - Arch Linux ARM support / Re: Update: C1000 / Akita support
« on: May 02, 2025, 02:03:51 pm »
Another thing: I know Xscale can "scale" the CPU frequency.
Can the Linux Kernel reduce the clock frequency at run-time?
It is useful to extend the battery usage time

if I use the PDA to write with { GNU/Nano, VIM, ... }
I do not need 400Mhz, I can very well work at 200Mhz


9
Zaurus - Arch Linux ARM support / Re: Update: C1000 / Akita support
« on: May 02, 2025, 02:03:21 pm »
I would like to comment on the lines of kernel code that activate the suspension when the power/on button is pressed.
to prevent the PDA/Akita from crashing if accidentally pressed

Code: [Select]
disable apm_queue_event() on key_suspend
--- drivers/input/apm-power.c.original  2025-05-02 17:58:24.140000000 -0000
+++ drivers/input/apm-power.c   2025-05-02 17:58:23.788000000 -0000
@@ -20,7 +20,7 @@
 {
        switch (keycode) {
        case KEY_SUSPEND:
-               apm_queue_event(APM_USER_SUSPEND);
+               // apm_queue_event(APM_USER_SUSPEND);
                pr_info("Requesting system suspend...\n");
                break;
        default:

10
Zaurus - Arch Linux ARM support / Re: Update: C1000 / Akita support
« on: May 02, 2025, 02:02:32 pm »
Code: [Select]
macmini2-intel kernel-5.4.229-arm-akita # ./mybuild-2024 2
[step2] compiling
kernel-5.4.229(arm/zaurus-akita)
| vanilla + patches from Void
| status:
|  boots(from SD)
|  boots(from CF-microdrive)
|  usb-lan DM9601 works
|  suspend
|    failure on c1k
|    success on c3k
|  irda/raw serial, added, to be tested
toolchain(armv5tel-softfloat-linux-gnueabi:2.40.0/12)
-----------------------------------------------
checking myhost as qualified_host ... success
checking .config ... success
checking blobs ... success
-----------------------------------------------
gadget_to_do(build) ... overlay/build
cleaning ............... done
gadget_to_do(clean) ... kernel/clean
building kernel ... success
-----------------------------------------------
gadget_to_do(binary) ... overlay/binary
gadget_to_do(sweep) ... kernel/sweep
app_body    =kernel.zImage
app_size    =5003576 byte
app_size_max=6000000 byte
checking size ... passed
gadget_to_do(binary_report) ... overlay/binary_report
macmini2-intel kernel-5.4.229-arm-akita #

that's how I compile kernels for all the platforms I support, mainly MIPS, POWERPC and HPPA2.
I wrote a "builder" in bash-scripting + C/89, to help managing patches, configuration, and checks

Every build comes with a "profile", which tells about
  • the toolchain, with constraints on the min and max versions of binutils and gcc
  • the ecosystem (it's called "qualified machines", can also be a chroot, or a container), to ensure you are using the right setup, at least "tested"
  • the final size of the kernel
  • the final file-format { uboot, elf, bin, zImage, ... }
  • etc...
Code: [Select]
checking .config ... success

Here, it checks a file in ensures that the .config contains options considered "essential", and that it does not contain options considered "to be avoided"
Code: [Select]
macmini2-intel kernel-5.4.229-arm-akita # cat profile/config_check.list
CONFIG_PANIC_TIMEOUT                 # without this, panic() loops forever

CONFIG_USB_NET_DM9601                # Davicom DM9601 USBv1.1 10/100 Ethernet NIC

not CONFIG_CMDLINE_FROM_BOOTLOADER     # do not allow the bootloader to pass cmdline
CONFIG_CMDLINE_FORCE                 # built-in cmdline
CONFIG_CMDLINE                       #
                                     # console=ttyS0,9600n8 console=tty1
                                     # noinitrd
                                     # root=/dev/hda2    /dev/sda2
                                     # init=/bin/bash
                                     # rootfstype=xfs ro
                                     # video=pxafb,mode:640x480-2
                                     # fbcon=rotate:1
                                     # (debug)
CONFIG_EXT2_FS
CONFIG_EXT3_FS
CONFIG_XFS_FS

CONFIG_IKCONFIG                      # save .config into /proc/config.gz

CONFIG_GPIO_PCA953X                  # set the GPIOs in Akita
....

11
Zaurus - Arch Linux ARM support / Re: kexecboot-size, max-size?
« on: May 02, 2025, 10:49:16 am »
If there was a documented jtag port, I would like to erase the entire flash, and reprogram it from scratch, in a more intelligent way.

strange that no one has ever thought of this ...

... another alternative, physically unsolder the flash chip, reprogram it in the lab, re-solder it.

we'll see.

12
Zaurus - Arch Linux ARM support / Re: kexecboot-size, max-size?
« on: May 02, 2025, 10:31:07 am »
Ok, so it's 1.2Mbyte max.

uboot ? yes, you can build a uboot to fit as a replacement for kexecboot kernel, but you have to port it yourself :) pxa support in uboot is not that recent I believe for pxa270 or any pxa.
kexecboot was a sensible choice back then...and still is

modern kernel (v5, v6) just don't fit into 1.2Mbyte
uboot is much smaller in size (<800Kbyte) and has much more potential
- tftpboot both kernel and ramrootfs
- ability to script warm boot, or cold boot

it is not a problem for me to support u-boot, even from scratch.
I will look into this.

13
Zaurus - Arch Linux ARM support / Re: Update: C1000 / Akita support
« on: May 02, 2025, 09:59:19 am »
and as per above hint from ant:  CONFIG_GPIO_PCA953X=y is set in your kernel ?

yes

14
C1000/3x00 General discussions / Re: C1000 As A Ir Remote
« on: April 28, 2025, 08:10:34 am »
interesting  ;D

15
Zaurus - Arch Linux ARM support / kexecboot-size, max-size?
« on: April 28, 2025, 07:47:23 am »
I'm a bit confused by what I read online.
I wonder:
1) what is the maximum size of the kexecboot executable? < 2Mbyte? or <1.2 Mbyte? Different things are read online.
2) isn't it possible to repartition the flash and use the entire flash to contain kexecboot or something similar?
3) why is there no interest in u-boot?

Pages: [1] 2 3 ... 5