BeagleV-Fire Stuck at HSS (ipi_poll_service) after Flashing Custom Gateware

BeagleV
1

Hi all,

I think I’ve soft-bricked my BeagleV-Fire after flashing a custom gateware. It currently hangs at: [1.706737] ipi_poll_service :: [init] -> [monitoring]

스크린샷 2026-03-05 182230
스크린샷 2026-03-05 1822301146×993 43.7 KB

What happened:

  1. I modified the MSS and added an AXI Master FSM.

  2. I accidentally left the simulation value for INIT_COUNT (only 20 cycles) instead of the required delay.

  3. It seems the FSM tries to access DDR before it’s ready, causing a permanent bus lock.

The problem: I cannot interrupt the boot via serial (ESC/Enter don’t work), and the flashing tool can’t connect to the board anymore.

I followed the steps in the Help! I broke my board guid

e, but I was unable to interrupt the HSS or U-Boot stages as the serial console remains unresponsive to input.

Is there any way to force a recovery or bypass the gateware load without a FlashPro JTAG programmer?

Please let me know if you need more details. Thanks!

2

People have reported success with other FT2232H-based JTAG programmers,
but you need to reach Linux in order to re-program the board “the usual” way, sorry.

(the FP5 is nothing but an FT2232H hiding inside, but with a special VID:PID ofc.)

1 Like
3

Thanks for the tip! Do you know of any good docs or guides on actually doing the recovery with an FT2232H adapter? Would really appreciate any pointers.

4

Sadly not. Was trying to illude to this fact earlier; hence the specific wording.

You can however start the standalone version of flashpro to check for cable detection.

It does involve reprogramming the eeprom of the adapter with the correct VID:PID;
a Goggle search should net you the exact values.

I was lucky enough to be furnished a FP6, courtesy of Microchip,
so I’ve never been in your exact situation.

Should you get far enough to actually do some JTAG programming (and I hope you do),
please be aware that you need the exact same build-version as you currently have,
otherwise the systemcontroller will notice, grab the faulty bitstream and you’ll be
right back where you started…

1 Like
5

My FP6 has a VID:PID of 1514:2009, so an educated guess would be 1514:2008.
(or something in that neighborhood)

1 Like
6

Thanks a lot, really appreciate it!