Skip to content

boards: Add olimex-teresI#26

Merged
samueldr merged 1 commit intoTow-Boot:developmentfrom
samueldr:boards/olimex-teresI
Jun 7, 2021
Merged

boards: Add olimex-teresI#26
samueldr merged 1 commit intoTow-Boot:developmentfrom
samueldr:boards/olimex-teresI

Conversation

@samueldr
Copy link
Contributor

@samueldr samueldr commented Jun 2, 2021

I do not own this board, it will need a tester before this is merged.

@Thra11
Copy link

Thra11 commented Jun 6, 2021

I created an SD card with the Tow-Boot disk-image, followed by two more partitions, a 20M firmware partition (empty except for a single file, config.txt), and a bootable system partition containing a nixos system (These two partitions are copied from another SD card with a working system using u-boot). The internal eMMC does not currently have any bootloaders or bootable partitions on it.

If I fit this SD card, power on the system, and leave it alone, it boots just fine.

If I interrupt it by pressing Ctrl+C when prompted, it shows the menu, which is navigable using the keyboard. However, all of the "Boot from *" options fail, even "Boot from SD", despite there being a (clearly) bootable SD card fitted. Will continue to investigate...

@samueldr
Copy link
Contributor Author

samueldr commented Jun 6, 2021

A fresh build from the current tip of development or using that first release? It's possible cancelling boot with ^C is cancelling the commands list if you used the first release. DUH... It's a build from this PR... disregard this.

Note that the "firmware partition" you're adding is useless; in the NixOS generic sd image, that "FIRMWARE" partition is the IBF (Initial Boot Firmware, read: U-Boot) exclusively used for the Raspberry Pi family of hardware.

Is that "bootable system partition" partition marked as bootable? Starting from the disk-image.img file it would be GPT. See #25 for some notes about setting a GPT partition as "bootable".

I guess I could test on any of my A64 targets for this. It wouldn't surprise me if the Boot from __ options are failing due to some weirdness, impurities and environmental pollution. I might have seen a similar issue previously while trying to boot some targets.

Copy link

@Thra11 Thra11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have logged the problems with the menu as #29, which seems unlikely to be specific to this board, so looks good to me.

@samueldr samueldr merged commit d263c8d into Tow-Boot:development Jun 7, 2021
@samueldr samueldr deleted the boards/olimex-teresI branch June 7, 2021 04:59
@Thra11
Copy link

Thra11 commented Jun 7, 2021

Is that "bootable system partition" partition marked as bootable?

Yes. I added a legacy bootable flag in fdisk.

Note that the "firmware partition" you're adding is useless.

I believe you're probably right. In theory the config.txt is supposed to be read to set debug=on, in order to enable/disable the headphone jack serial output (It doesn't have a physical switch like the pinebook-pro and pinephone). It's unlikely to be doing anything at the moment, just lying around on a random partition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants