Unable to get past "Looking for BBF..." #171
-
|
Hi there! Fantastic work with this project! I'm really looking forward to making little tweaks to the firmware, but without having to make the leap with my actual printer. However, I'm stuck at this stage: Here's what I have done:
I believe that I read through everything on the wiki several times, and accept that I'm probably doing something wrong. Any pointer in the right direction would be a huge help! Things I have tried
✗ ./build/qemu-system-buddy -machine prusa-mk4-027c -kernel ../Prusa-Firmware-Buddy/build/products/mk4_debug_noboot.bbf
# FIXME: OTP and engineering bytes should be split.
No -mtdblock drive specified, using default Prusa_Mk4_xflash.bin
No -pflash drive specified, using default Prusa_Mk4_eeprom.bin
No -pflash drive specified, using default Prusa_Mk4_eeprom_sys.bin
# ScriptHost: NOTE: Duplicate context name (thermistor) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (thermistor) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (thermistor) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (thermistor) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (cs30bl) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (cs30bl) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (heater) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (powersource) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (oc-latch) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (oc-latch) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (oc-latch) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (oc-latch) with different pointer. Incrementing ID...
# ScriptHost: NOTE: Duplicate context name (fan) with different pointer. Incrementing ID...
WARNING: icount is disabled. AT21CSxx EEPROM will NOT WORK!
WARNING: use -icount [number] to enable it.
# CPUCLOCK set to 16000000 Hz
# Systick frequency (REFCLK) set to 2000000 Hz
qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hey there! Thanks for the kind words. The good news is you did everything right so far, and you're an unfortunate victim of documentation that hasn't kept up with the state of the firmware. (Sorry about that... As of late I've had limited spare time to move this project forward and keeping the docs up to date is a sacrifice I've opted to make in favour of (attempting) to keep up with current printer models and firmware functionality changes. PRs and other contributions to improve things are more than welcome, though even just asking the question here is already helping, since it means I have to explain things in a place where others may find and benefit from what I write ;) ). Now, to your issue(s): Firstly, let me just clarify an important distinction between a "boot" firmware file built from the buddy-firmware repository, and the bootloader file. These are VERY different:
With those distinctions in mind:
That's the first complication. Regardless of the path chosen to load the executable code (BBF or _noboot.bin), we now come to the second complication:
The typical way to facilitate this is using the USB-storage functionality of the simulator to either pass through a folder on your hard drive (or a USB drive image, though this is more complicated) which is treated as a virtual USB drive. This is also one way you would get gcode "into" the simulated printer. Please let me know if that helps you get back on track! ¹Theoretically, this process for handling a boot.bin is the same as for a BBF. However, there's no convenient way to identify whether a .bin firmware file is compiled as |
Beta Was this translation helpful? Give feedback.



Hey there!
Thanks for the kind words. The good news is you did everything right so far, and you're an unfortunate victim of documentation that hasn't kept up with the state of the firmware. (Sorry about that... As of late I've had limited spare time to move this project forward and keeping the docs up to date is a sacrifice I've opted to make in favour of (attempting) to keep up with current printer models and firmware functionality changes. PRs and other contributions to improve things are more than welcome, though even just asking the question here is already helping, since it means I have to explain things in a place where others may find and benefit from what I write ;) ).
Now, to you…