[ GXB172 - 50W Single Cell 17mm Boost Driver! ]

Hello all,

[Update Jan 2021 - This driver has evolved to the Lume X1, check it out here! https://budgetlightforum.com/t/-/65319 ]

It's been a long while (half a year or so?) since I've been back to BLF, and I hope everyone is having a good start to 2018! Over the past some two weeks and a half a lot of things has happened so I'd thought I'd share some here. It all started from when I found some time to do a proper write-up for my GXB17 driver which you can read in detail on my webpage here.

Above - the GXB172 in a brass Convoy S2+ Pill

[New!] - Above, 20mm version, the GXB202 with larger passives and more edge clearances.

Summary

I'd like to share a little evolution of my previous drivers. I've called it the GXB172, and it's very similar to the GXB17 driver, but is capable of handling 50W! The driver has been tested to ~7.2V at 6.5A output so far. It's a little silly and not at all practical because any flashlight holding a 17mm driver would most likely not be able to sink all the heat and the light will throttle down hard really quickly, but it was still a fun project getting it to fit a 17mm form factor since it'd be really much easier (and more powerful) with discrete FETs for say a 30mm driver! It's getting pretty late here so I'll post this for now and write updates! Eventually I'll be writing up a detailed page with all my design details and source and schematics etc on the GXB172 page.

Project Status (End Mar 2018)

Currently the GXB172 is verified to be working. Basic functionality checks out. One driver has been installed into a Convoy S2+ for real-life testing. All basic firmware features appear to work as intended, except thermal throttling needs a bit more fine tuning. See the first GXB172 build here: https://budgetlightforum.com/t/-/50373. Driver has so far been tested with XHP50B at 6+A, Nichia 144 at 4.5A, and XHP35 HI at 2.5A (14.7V) (new).

Feature List

Here are some of the general features, many more to come with more work to be done on the firmware. In no particular order:

  • Input - Nominally 1S (e.g. single 18650), ~2.7V to ~4.4+V, But works with 2S as well if the right Vreg/LDO is used (and firmware written to take advantage of this)
    • My guess is that if the flashlight can hold 2S, it should be big enough for a bigger driver :P
    • If you're thinking about something like a 2S 18350, my thinking is, why not just go for a single 18650? In the past a 2S might have been used for a non-boost driver, but this driver helps to overcome that gap :)
  • Output 6V - Tested up to 7.24V at 6.5A, around 5mA for moon-light mode with a Cree XHP50B
  • Output 12V - Tested up to 14.7V at 2.5A, and around 2-3mA for moon-light mode with Cree XHP35HI
  • True Constant Current control, no PWM flickering, 1024 linearly-spaced brightness levels
  • 17mm Diameter, 4 Layer PCB
  • Attiny841 programmable microcontroller
  • Ultrasonic switching - never drops below 23kHz so no high-pitched whine even at moonlight mode
  • Candle-mode - just for fun, but simulates a flickering candle (working on simple algorithm to make it 'look right')
  • Accurate digital temperature sensing with digital temperature sensor
    • Much more accurate and and consistent than NTC or thermistor
    • PID temperature regulation - automatically varies output on high modes to maintain set temperature
  • Battery Voltage Sensing (for 1S and 2S) and low battery cut-off etc
  • E-switch support (e.g. can work with Narsil with some tweaks, firmware work required)
  • 3x additional GPIO
    • 2x jumpers / 1x pads(e.g. can be used to say configure for up to 8 different modes without firmware change)
    • Alternatively can also be used to drive extra LEDs for indication lights, button backlighting, buzzer etc
  • EEPROM Memory
  • Firmware Support (in progress)
    • With a suitable host, I'm very sure I with a little bit of work, this will work just fine with a modified Narsil E-Switch firmware
    • Likewise with Biscotti / Bistro, this can work as well since this driver has hooks and hardware for both OTC and OTSM
    • However, there are some non-trivial modifications needed to work with this driver due to many aspects, so I've made my own simple firmware for now (more discussion later)
  • Efficiency >90%+ for most output levels, over 95% at 1A output.

Background

As you may know, my GXB17 and GXB20 project started when I wanted to make a really bright (2000 lumen) but small flashlight powered by a single 18650 battery. Back when I started the GXB20 project, I don't quite recall if there were any affordable single-cell XHP50 lights around. So this changed I was discussing the GXB projects with a friend, and found that he recently bought a new Zebralight SC600Wiv+, which is a small single-cell light which also does 2000 lumens from a single XHP50!

Not only that, I was also told that there were some new ~3800 lumen single-cell (albeit 26650) lights around which were all just released late 2017 (while I was away)! Specifically, these were the Imalent DN70 and the Thrunight TC20. My thoughts started from "how could this be!!??", and quickly turned to "how can I improve on the GXB drivers to achieve the same output..?".

Granted these two (and I'm sure there are more now on the market) flashlights used a very high power XHP70 LED. But I recall that Texas_Ace and Djozz did some tests previously on XHP50 LEDs and found that if driven to a pretty ridiculous 6A or so, one could achieve close to 4000 lumens! With this, I had a new goal - make a ridiculous driver capable of driving a XHP50 LED to 4000 lumens in the same 17mm driver size. I could use a XHP70 but I really wanted to keep the theme of a ridiculous driver (because such a small host with such a large drive power is thermally limited a few tens of seconds of operation), and use the same Convoy S2+ or similar 17mm flashlights for my new build (where I don't think the XHP50 would physically fit inside the reflector).

So this was the start of the GXB172.

Design and Operation

My GXB17 and GXB20 drivers both used a fairly decent boost converter IC, in fact, the most powerful fully integrated one which I could buy on the market, the TPS61088. However, in order to drive an LED at 6A, it will need something like a V_fwd of 7V (42W output), or about 50W input. From a single cell, (expecting voltage drop to say 3.5V), I'd need something capable of ~15A or so. But the TPS61088 is only good for 10A, or close to 12A peak. How to drive it without resorting to external FETs and a multi-board construction?

As all hobby EEs do, the first thing I did was to do was to do a quick parametric search to see what options were on the market, and behold! I found some new components which I had not seen before just half a year ago! Previously the TPS61088 was the high at 11.9A! This new Boost IC turned out to be the Monolithic Power Systems MP3429/3431, both essentially identical except the xx31 having an adjustable current limit. This looks like it'll fit the bill!

[More to come - I'll continue updating this page later!]

Driver Development

The moment I found the new IC I was pretty excited and I literally spent a weekend afternoon creating a super simple schematic and rushed off a dev-board PCB to be made!

I knew that I wanted to incorporate some fun new features which I thought of only after developing my GXB17 and GXB20 drivers, and I figured that a simple 'dev board' would allow me to (1) much more easily probe the board and (2) allow much easier firmware development. For control system, I had previously taken apart a H1-A 22mm boost driver and I decided that the control system was better since it used fewer components, so I have adapted it with changes. Essentially the control takes a low-side voltage measurement from a sense resistor, and compares it with an analog voltage generated via PWM from the microcontroller. For this to work, a good quality low-input-offset Op Amp is needed. In addition, the last time a few people suggested to me to use an ATtiny841, but at the same time I also wanted to try other MCU options, so I also added hooks for soldering on a second MCU (the Atmel Attiny1616 is an interesting candidate since it's one of the new ones after the Microchip acquisition), but for now I've gone with the Attiny841 which is much more capable than the Attiny85 or 84A.

As you can see the dev board allows me to connect a whole bunch of probes to it, my AVR ISP programmer, as well as input and out via screw terminals, debugging LEDs, an E-Switch for E-Switch development, and two footprints for different MCU options if desired.

With the design optimized after tinkering around with the dev platform, I then designed the PCB and sent it off for fabrication!

(slightly older version)

This time I decided to save myself some trouble routing in 2 layers, and went with a 4-layer stackup, since I realized that the cost for the PCB really is marginal since the PCBs are so small. This made routing very easy and it was done much faster than my previous layouts, and many fab houses including OshPark are readily available to anyone who wants to make their own.

(current Rev A version)

Above is an updated version of the layout which I sent to fab, and to show a comparison of what swapping out the inductor for a bigger one looks like. The big inductor will have better performance at the downside of increased costs and obviously, size! It may not fit many pills due to the height of the inductor. This is Rev A of the driver and I'm sure there will be a Rev B!

The PCB was received from the fab and soldered up as shown in the first image at the top of this post!

Firmware

Currently the firmware is a simple, basic one. There are some specifics which need to be done to ensure the GXB172 works properly so it's not a naïve port of Bistro or Narsil to make it work, but this will be done in the future. Meanwhile, I hope this charge gives a good idea of what the driver's existing functionality is.

Results

So it turns out that just after I visited this forum again and updated my old GXB17 thread, Agro informed me that Schoki had already started a 17mm boost driver with the same boost IC as well! Unfortunately I had already sent the PCBs to be made so I guess I really should have visited this page earlier and saved myself all this trouble >.<.... doh!

Anyway I was able to take some measurements! In this test, I wrote a very simple test program which ramps up the LED current from 0 to 6.5A.

Above you can see the input voltage in yellow from a LG HG2 lithium battery (excuse the voltage drop, my battery cables were fairly long!.. and I had to use a battery since I had maxed out the 8A of my power supply!), the output voltage (magenta), the output current (green) and the switch node (cyan). The driver was hooked up to a XHP50A LED on a copper MCPCB and clamped onto a heat-sink (same as the one in the photo above).

Looking at the peak of the current drive, the GXB172 has an output of some 7.24V at 6.5A (47.06W)! This was at an input voltage of 3.4V and about 15.6A on the input (clamp meter) for a total efficiency of around 89% (much higher at more 'reasonable' drive levels!). This is about as high as one can go without increasing inductor size (e.g. going up from the Coilcraft XAL7030 to say the XAL7070 but those look pretty ridiculous!) and dropping the ripple current, since we want to have some headroom above the inductor and switch peak current! So far it seems like the driver is not thermally limited per-se, i.e. the LED produces so much more heat that it'll end up heating the driver up more than the losses in the driver.

12V LED Configurations (Apr 2018)

GXB172 has been successfully tested with just about 37W output drive on a XHP35 HI LED. Measured LED current was 2.50A at 14.7V.

Work is also underway to develop a 20mm driver form-factor (GXB202).

First Build - Real Life Testing (in progress Mar 2018)

Currently the GXB172 is verified to be working. Basic functionality checks out. One driver has been installed into a Convoy S2+ for real-life testing. All basic firmware features appear to work as intended, except thermal throttling needs a bit more fine tuning. See the first GXB172 build here: https://budgetlightforum.com/t/-/50373.

Current the driver has been set up with a Nichia 144 6V LED driven to 4.2A.

I'm also toying with the idea of implementing this in E-Switch mode (e.g. with the Convoy S9), which will give us much better performance since we bypass the switch entirely, and it's also much safer on the electronics (15A+ interrupt current is not a good idea! But neither was making a 50W driver in the first place :P).

Meanwhile, in order to handle the massive current without too much voltage drop across the switch (can be as high as 0.5V or more at 15A even with a good switch!), I made a companion FET switch for 1-3 milli Ohm switch resistance.

Please see this thread for more information: https://budgetlightforum.com/t/-/50404.

Frequently Asked Questions

Many of the questions I've received are the same, so I thought I'll make a little FAQ section!

  • Is this driver for real or are you making this up?
    • It's not real, but actually working decently well! I'll be passing some drivers to forum members for testing soon, but meanwhile, check out this video of a preliminary GXB172 in action in a Convoy S2+.
      https://www.youtube.com/watch?v=M-_C1XHUgQw
  • What is the status of this project?
    • Hardware seems to check out good. Basic firmware seems stable. Some tweaking needed for thermal control. However, still work needed to be done to port the popular Bistro / Narsil firmware over, which will take some time. However the driver as it is, is working!
  • What firmware does this support?
    • Currently the driver uses a Attiny841 MCU running my own firmware. It's similar to the BLF A6 firmware with a little less configuration features at the moment, but adds additional capabilities like candlelight mode, smooth ramps, PID temperature control etc. Eventually I hope to achieve parity with Bistro / Biscotti and Narsil, but that is going to take a while since it's not a simple MCU change, but rather it needs to handle a bunch of differences unique to the GXB172, which are not present in the standard 7135+Fet combination
  • Are you offering these for sale?
    • Not yet! I don't plan to make any money from this since it's just a personal fun project. However it seems like a lot of people are interested. Yet I do not want to release a product for sale which is not 100% solid. That said, regardless of how long it takes to get to a solid state, anyone will be free to make their own driver at their own time if you want to! :
  • Will there be 20mm version?
    • Yes! Because I have some SK98 hosts to upgrade from my GXB20 driver. In fact, going up to the 20mm size allows me to add even more cool features and better layout to the driver, i.e. it won't just be a copy paste of the GXB172. Stay tuned!
  • Will there be >20mm versions?
    • Not sure, but currently I have no plans for >20mm versions. The reason? If you want to go higher, there are far better options than the architecture as designed in the GXB172, e.g. you can use discrete external FET switching solutions since space is no longer a constraint. The uniqueness of the GXB172 and 202 are its small size. Sure I could easily make the same layout on a larger PCB, but that seems contrary to the original ethos of the GXB series of drivers. :) Anyway we'll see how that goes when we have a successful GXB172 and 202 first.
  • Will this work with a regular tail switch?
    • Of course! However you may encounter problems if your driver is configured for max drive. For example, suppose you're pulling say 12A from the battery, and your battery voltage drops to say 3.5V. You have a switch with resistance of 30mR. The total additional voltage drop across is 0.36V, so the driver only sees 3.14V. This may cause the driver to want to draw more current to maintain output power, and current increases. Eventually you will hit the current limit or the driver voltage drops too low, and the driver falls out of regulation. As a result, performance is not guaranteed unless you know what you are doing, since the driver is capable of pushing a lot of amps.
  • Will this work with 2S configuration?
    • The hardware supports this, IF you are trying to use this to drive a 12V LED. However a little bit of firmware needs to be done to handle the higher voltage to make sure the battery sensing is accurate, and some resistor values may need to be tweaked. But otherwise there's no reason why it won't work.
  • Will you be releasing the design, BOM, schematic, etc?
    • Don't worry, this project is not for private use - it's meant to be public and free! As with my older projects, I'll be releasing all of them for free under the creative commons with hopefully useful documentation. I'm still working on the design but it'll all be up on my website available for you to make your own and/or make improvements if you wish!
  • Is there a place I can get the PCBs from for now?
    • Yes you can order your own GXB172 Rev A PCB on OSHPark yourself right now here, but more details to come..
  • How about the firmware?
    • Same thing with the firmware! :)
  • I want to assemble this myself, is it possible?
    • Yes, but I highly recommend having access to some sort of magnification (EE microscope or magnification camera), a small soldering iron tip with very thin solder and needle-nose tweezers, as well as a reflow oven if possible. All my prototypes are assembled at home, so you can do it too with some experience!
  • How long does the light stay in turbo before throttling?
    • At 50W, from a ~20C starting temperature, it takes less than 30s for a Convoy S2+ to heat up to more than 60C at the pill, where thermal throttling begins. You can either increase the thermal limit from 60C to higher, or use a better host with better cooling.
  • Doesn't this mean this driver is useless?
    • At turbo I suppose! But that's the point of the GXB series - to make a ridiculous driver! To be fair, the Emisor D4 also runs at turbo for just about half a minute before also throttling down. Also keep in mind that with PID control, as long as you keep the light cool, it will maintain maximum output for as long as the batteries can sustain, even when it has throttled down (e.g. you dunk it in snow after it starts throttling, and the light will go back up to full output). In addition, you can also adjust the modes yourself to set the max to a more reasonable 10W, then it works just fine as a normal everyday driver, but with the added bonus of being able to use some beautiful 6V or 12V emitters, via a single cell
  • What hosts does the GXB172 fit into?
    • The base diameter of the GXB172 is 17mm, so any host which holds 17mm should allow the driver to fit. However, the main size constraint is the large inductor on board. For best performance, the 7mm tall inductor should be used. A smaller 3mm can also be use, but at the cost of reduced performance and regulation, and reduced efficiency. If possible, the larger inductor should always be used if space allows. I know this driver fits perfectly in a Convoy S2+, but I have no other flashlights to test otherwise, so YMMV!

Hopefully this will be a driver which people will find useful.

Thanks for reading and I'll continue to post updates as this project progresses.

So excited to see more development on this, many thanks for sharing. Maybe one day either of these drivers will be available as a kit or via Oshpark, I really like soldering and building drivers.

Wow, this looks awesome!
Thanks for sharing. :laughing:

Nice! This would be remarkable in a 17mm driver

“Driver is good for 20V output, so I’m expecting a ~14V close to 3A output for that configuration (working on this soon)”

I would like to see this (use this) in a 20, 26, 30mm driver size… :wink:

Sounds great!
Way more features than expected.

Can’t wait to learn more about efficiency at lower modes. And 12V.

ADDED:
Now it would be good to merge both MP3431 developments…

600kHz fixed-frequency
may dont like
4-layer stackup
Also
dev-board PCB
seems the reason why
the driver is not thermally limited per-se
In real life driver inside S2+ brass pill can overheat if loss power is above ~2W.
I would prefer to see usefull product, would it be 20mm or 17mm, 25W or 50W. Better have 20mm driver with 25W output that can work for hours than 17mm with 50W output restricted after 30-40sec by thermal protection.
H1-A overheats in 2 minutes inside eagle eye X7. I would like similar driver that can work 15+ minutes was available at the market so I could suggest it to use with my last project.

I am shocked how similar our top pcb layer looks like. But well done :+1: , I’m about to order my PCBs today or so.
And you need to correct something: I’m sure the driver won’t output 20V, 16V is pretty much the maximum.

@kiriba-ru: Why is this driver not useful? You can select your maximum power yourself with some resistors changed. Then you have less overheating problems.
And you can’t expect a driver to work at a ridiculously high efficiency, 90% is pretty good already. I would put more focus on the thermal path of the driver to the head/pill, and the heat sinks on the flashlight should be better. Just a ring around the driver is not enough to cool it. When you compare a flashlight “heatsink” with a proper CPU heatsink, it’s quite clear that the flashlight won’t be able to cool the LED and the driver combined.

That was an interesting read :slight_smile:

Thank you, loneoceans, I’ll be following along as you work on it!

Good stuff! You plan on selling these?

Might be interesting to make a pill for my Brinyte B158 with XHP70.2 or 50 LED.

The XAL7070 increases the efficiency for 25-50W Output you should use it
The ripple comes from the inductance, DC losses and saturation on the XAL7070 is better
Also 1206 capacitors are better than 0805s especially when the driver gets hot

Would one 1210 cap be better than two 0805 caps?

one 10uF X7R 25V 1210 is definately better than 2 0805 X7R 10V 4.7uF

Only thing I do not see mentioned is being able to accommodate 1S or 2S input in the same configuration. Lights like the Convoy L2 that have an optional extension tube would really benefit from this.

I do not understand most of the thread otherwise but I cant wait to try out some of these new boost drivers

This I asked in Firmware topics and wrote PMs to Tom_E and Toykeeper
I got no real solution

It is no big deal if it gets integrated in Bistro and Narsil, but I am not capable of doing it

Welcome back Lone. I wrote you emails months ago and thought you’re already left us. But here you are with your crazy driver project. Great job Lone!

- Clemence

This looks awesome thanks for sharing the project with us.

When you solder the smaller components do you use a soldering iron or heat gun?

Answering comments:

Thanks FPV. Yes once I finish the firmware and done some proper field operation and stress testing, I'll put everything online so you can order your own PCBs and put your own together! However do be warned that you do need some sort of proper setup to either reflow / hot air this or put this together under magnification. Meanwhile I'll start putting up my GXB172 page on my website as I go along.

As for sales, we'll see how it goes! I certainly wouldn't want to put something up for sale if the firmware is not up to scratch or if the driver has issues. Suppose all is sorted out, I might do a small run, or send for PCBA which would be much nicer, but it depends. Morever Schoki / Lexel are already working on driver and it seems they have more history of releasing drivers, so you can go with that route as well! I just had no idea it was already in development when I made the GXB172.

KawaiBoy1428, whoops I meant to say 16V, but yes it's good for driving LEDs like the XHP35 (12V+), and by extension, also good for 9V operation. I do hope to make a 20mm version with even better performance (better passives) in the future to replace my GXB20, but I'm not planning to make this design any larger. The reason being that any larger would allow me to use an external FET solution and it's really much easier then to make a 50W or even higher power driver - no need to constrain myself with this particular topology. That's the good thing about the 'dev-board', easy to do tests like this.

Kiriba-ru, you are absolutely right! The driver and LED setup for any flashlight that can accomodate a 17mm driver would definitely overheat at 20W, much less at 50W! Drawing this amount of power from a small cell is also ridiculous. However, that's the premise of the project - to make a ridiculous driver. As I've mentioned, it's fairly useless from a practical point of view, but practicality was not the main point of the GXB172, at least not in 50W output. I have no illusions that 50W is anywhere near a practical drive power for a 17mm-driver flashlight.

Regardless, the driver should still be in the upper 90s% for most of the range from ~100s of mA to 2-3A output (will measure soon) so it's still a fairly efficient driver at realistic drive power.

For example, the Emisar D4 has a 3000+ lumen direct drive mode, but this lasts for only 10s of seconds, before the light drops down steeply to some ~300 lumens or so by thermal regulation (based on here https://www.youtube.com/watch?v=GVj7NnAj_Ps). Again depending on what you set the thermal limit to be and what the external temperaturate is, my guess is that the Convoy S2 can probably only handle on the order of 3 to 5W of continuous run time (e.g. headlamp), and likely not much more than 10W (handheld light) for any reasonable temperature limit (taking into account the whole system including LED, driver and battery).

And as Schoki said, because the driver is in fact much more efficient at lower drive power, this makes it a pretty good driver for 20W operation I think. In fact, in real life, I'm going to set my everyday mode limit to be around 25W operation. This is very easy to set and the 1024 current limit steps make brightness control still fairly high resolution even at lower powers (or you can swap out some resistors to make this even better!). I'll be able to do some more detailed thermal analysis later, especially when I get it into form factor.

Also Schoki, thanks for your comments, and I see the renders of the driver Lexel posted! Is that the driver you two are working on together?

Yes I agree the top (inductor side) layout looks similar, but I guess come to think of it it really falls out into place just based on how the (few) power components and traces needed to be laid out, and what we can fit into the same round PCB. I did start layout based on the reference layout in the datasheet, and used a single 1210 capacitor for input and output rails, but I couldn't get it to fit in a reasonable way, so I split them into combinations of smaller caps instead and that's basically the only way I could lay it out. The rest of the compensation network and feedback then just slots in the leftover space. I also initially use through-holes for the LED outputs but I switched them to large pads instead just to make routing on the other side easier. Also good catch on the max voltage rating, I meant to say 16V!

Its all black magic to me but know its all real good stuff. :slight_smile: :beer:


Lexel you're absolutely right! The XAL7070 and 7030 have essentially identical pads so I made the pads fit both inductors, so you can choose whatever you want. Some pills like the Convoy S2+ have a lot of space so it definitely makes sense to go with the big inductor. Others have less space and I've verified it works OK with the smaller inductor too. But like you mentioned, the 7070 helps in reducing DC losses (and thus also less likely to cause the inductor to drop inductance due to heat), and that we can use more inductance for less ripple and less RMS current losses and switching losses!

As for the capacitors, yes definitely larger and higer voltage rating with better dielectric is more desirable. In fact I did change some of the pads to 1206 before I sent it off for fab last week. Since the inductor is so fat, it's also possible to stack MLCCs on top of each other. Currently I have 94uF on both the input and the output at 16V, though we could do something like a 138uF 10V on the input and 66u 25V on the output, and more with stacking. Finally, I also found some nice bronze springs from Kaidomain which have a ~5mm top and ~8mm bottom. The high drain cells all have fairly large flat tops so I'm planning to try to use those springs in reverse (since my spring pad is very small to save space), but I suppose it doesn't really matter since we'll need to bypass them anyway.


Well the way I have it set up should work just fine I hope with perhaps a change in a resistor or two. The LDO max input is above 2S, and my battery voltage divider also takes this into account so it's a simple firmware change to have it running with 1S or 2S with auto-detection. The downside however is that because this driver is fairly specialized for the application, for best performance ideally one really needs to configure it for either 6-7V out or 12-14V output. For example, if I really wanted to drive a 6V LED hard, I'd choose input and output caps specifically for that purpose which would not work well for a 2S input. Likewise for 2S operation, I can choose a larger value inductor for less ripple and a more regulated output with lower peak switch current. So in short, it can work, but it will not be near optimal. That said, if you're just planning to run at fairly low power levels (<20W), I see no major problems.


Hello Clemence! Yes thanks also for your help in getting Nichia LEDs to the community! I ordered some from you recently so hopefully I'll get to pair one of the 144s with this project.

Thanks for your kind words! For soldering, it depends! Typically for stuff like this I use a stencil and reflow it in an oven, but for one-off small boards like these (at least for now), I typically use hot air for the stuff with pads underneath, or in this case, the big indutor too. The rest I either use hand-placed solderpaste with a needle and hot air it, or use a tiny tip soldering iron and needle tweezers. Typically I do this under magnification.

Thanks MRsDNF! I hope to get this inside a flashlight soon when the host and boards arrive, and when I finish whatever firmware I'm working on right now.

In which mode are you running the boost IC?