swishy
Kia ora All, I’m currently porting nerves to the Khadas VIM3 board and have got to the point its booting fine however fwup appears to be corrupting the written image - I have tested both fwup 1.13.2 and fwup 1.14.0 -
Khadas VIM3 (AMLogic A311D)
Mainline U-Boot 2024.01 (512-byte offset for SD card)
MBR partition layout with bootloader at sector 1 (512-byte offset)
Kernel panics with VFS: Unable to mount root fs on unknown-block(179,2)
The generated .fw image however contains a mountable squashfs filesystem
Corruption appears to occur with both mix burn and mix firmware.image - file headers appear intact but data is corrupted on raw_write() to root partition after byte 35 onward. Its reproducible using both zip and xz compression.
At the moment I’m getting a boot-able image by extracting the generated .fw file and using dd to write to sdcard
e.g. dd if=/dev/sda2 of=/tmp/extracted.img bs=512 count=524288
Passing the following in target.ex to use xz compression
config :nerves, :firmware,
mksquashfs_flags: [“-no-xattrs”, “-quiet”, “-comp”, “xz”]
I’m assuming its something stupid I’m doing, any insights would be appreciated.
Dale.
Where Next?
Trending in Questions
Other Trending Topics
Latest Nerves Threads
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 9- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lawik
How are you flashing the device?
Does it show up as a USB mass storage device or how sre you using fwup/dd to write to it?
fhunleth
Hi @swishy,
It would be helpful if you could sharing your project that reproduces the issue.
Normally when people report corruption issues, they’re due to having some other part of the fwup.conf overwrite the part that’s getting corrupt. That’s what I’d check.
Using xz or gzip for SquashFS compression shouldn’t make a difference, but I’d stick with gzip to minimize the number of changes you’re making.
swishy
Yeah USB mass storage device at the moment and mix burn to write image to sdcard card - as mentioned uboot / boot sector are written fine root fs ends up corrupted so having to manually write using dd at correct offset.
swishy
I’ll get the repo public later today - just cleaning up a couple of hard codes in the boot configuration so they are following nerve conventions correctly
swishy
ok repository is available here ST8VRT / nerves_system_vim3 · GitLab
fhunleth
Thanks. I just tried your repository and got an error when running
fwupdue to the U-Boot environment block and U-Boot image overlapping. I know this isn’t the problem that you reported, but I wanted to get a clean image before checking anything. I sent you a PR to fix the overlap.swishy
awesome thanks for that - not quite sure why I haven’t hit it as I have rebuilt the image about 2.5k times to date lol
swishy
Ok funny story - fresh checkout with your fix and it now boots fine using mix burn
, feel like the cache gremlins have bitten me again lol
lawik
Glad to see it got resolved