Search results

Actually, digging in a bit more, it looks like the extlinux configurations are already being generated by the debian package. From what I can see, it has similar functionality allowing a user.cfg to overwrite the automatically generated configuration. Unfortunately, this doesn't seem to have...

No I’m not subscribed to the mailing list. I should be I’ll get on that. Mostly I’m trying to bring the information to the general community and users rather than just developers. This is why I’m starting to build the wikis. They’re on gitlab for now since the current wiki access is broken at...

Ok! So there are some updates here. I have mostly stabilized the bootloader. I have decided on a method of handling user configuration and customization of the bootloader. It consists of a two-phase environment update system. The bootloader first loads boot.txt which defines the paths for...

That should work fine.

Ah so maybe extlinux is a good thing to keep and have the boot script be modified by PyraOS.

I am leaning towards continued use of uEnv.txt since it can be easily modified on the fly without needing to mkimage it. One thing I'm not very familiar with is using u-boot to detect and select the correct kernel/dtb/initrd given a few versions. I've never built an embedded Debian device...

Sure I can do so, but there has to be a default. Currently the default is 2A because that's what ED asked for and I don't see any reason why that should be an issue currently (in terms of compliance and hardware damage). I'm not going to change the default to 1A because one person wants it...

Working on this next. Got a start on this a month or so ago, but haven't been able to get very far until now. The kernel needs a new driver for this, so I'll be starting work on this probably next week once the bootloader appears stable.

Alright, so I finally have hardware and have made some pretty solid headway on the bootloader. Currently the bootloader is using boot.scr files to guide the boot process. Personally I think it would be a bit easier to use a uEnv.txt for loading the environment. Its a lot more friendly to...

That means it is probably configured as a DCP device, which does not perform any communication over USB but shorts together D+/D- to inform the host that it is a wall charger. You can learn more here. https://www.maximintegrated.com/en/design/technical-documents/tutorials/4/4803.html#3

The current setting is a limit. If the source cannot supply 2A, it will not use 2A. The charging current supplied is (should be) negotiated via USB 2.0 protocol between the bq24 and the charger. If the charger is “dumb” and just supplies current, there are hardware stipulations in the spec that...

For those interested, booting without a battery works (my charger circuit was damaged but is now repaired). I have also implemented fast charge configuration in the bootloader so it can charge at 2A immediately. The bootloader updates will be released soon, and the charging software will be...

First I’d recommend just reading up on Kbuild and poking around in the kernel to see how the system is built. The kernel is highly configurable and modular thanks to Kbuild. Then poke around in the drivers directory to read some of the driver code. In particular on the Pyra kernel, take a look...

Big big +1 for C Programming Language by K&R. If anyone is interested in learning kernel development, I don’t really know any good books for this. The kernel is constantly changing and being improved. Really the best way is to just dig in, read the code, and play with it. The Pyra is actually...

Keep in mind I said it doesn’t boot without a battery. That doesn’t mean that it won’t. This will be working soon enough.

This should be possible. From my analysis of the hardware, it should by default allow for the 500mA limit. My HW just wasn’t behaving this way. I’ve been working with HNS to try and find out what the reason for this is. Turns out my charging circuit was damaged in a few ways either by...

This is probably part of my charger chip issues then :) I’m currently going through the power management schematic with HNS.

The problem is not with the PALMAS, it’s with the battery charger. By default it limits current to 100mA. The hardware allows for an increase to 500mA but this isn’t being enabled for some reason. I’m currently investigating why this is happening and working on a fix. Right now the Pyra draws...

Nope.

Here's a photo of the shoulder button against the cable. I've since shaved it down but its roughly the same. I've been working on the bootloader, so haven't really even booted the thing :) I booted it fully once or twice and it didn't take very long. Maybe 10s, 15 max? I can do some...