开云体育

I have been successfully making some small tweaks to the 0.1.1 firmware. I would like to change the colors of the traces to make them more readable in sunlight. However, that tweak has not been successful. In main.c, I tried changing the trace_color array in config_t config. However, it does not seem to have any effect. What am I missing ?

Thanks,
Steve, N2IC

Change colors in this line. main.c

Standard
/* trace_colors[4] */ { RGB565(0,255,255), RGB565(255,0,0), RGB565(0,0,255), RGB565(50,255,0) },
Blue -> White
/* trace_colors[4] */ { RGB565(0,255,255), RGB565(255,255,255), RGB565(0,0,255), RGB565(50,255,0) },

Sorry, DMR...it doesn't work. Still blue.

I do a make - main.c recompiles, builds,etc.

do sudo make flash and the flash appears to install just fine.I'm using the config->dfu->reset and enter dfu, not shorting the pins.

73,
Steve, N2IC

I just tried it myself. Everything is working. Did you remember to click save before compiling?

Well, it doesn't work for me....

Tried:

1) Intentionally putting a syntax error into main.c to see that I was building the correct main.c.
2) Shorted the pins to put into DFU mode.
3) Changed all of the trace colors to (255,255,255).
4) Made a change in plot.c, to confirm that the correct firmware was being flashed.

The result is the original, default colors.

73,
Steve, N2IC

Try this one, instead of blue, white.
DFU Firmware.

Successfully installed your white.dfu. Still blue.

Hardware issue ? Some kind of flash memory that needs to be cleared ?

73,
Steve, N2IC

Yes, flush this firmware cleaning, then your own.

I got mine printed at the library

Very Happy
John VE3IPS

Well, that bricked it !

Installed CLEAR_MEMORY_DFU.dfu.

Tried to install any dfu after that - with and without the jumper. No good.
No DFU capable USB device available.

Next suggestion ?

I think that since you were not able to flash the firmware with changes in the color scheme, you have the driver for the firmware mode through dfu installed incorrectly. When connecting again, how is the device defined in the device manager?
What is the bit depth of the operating system, and the Windows system itself?

stm32 cannot be corrupted, since the bootloader is permanently sewn, and it is impossible to change or erase it.

I'm doing this on ubuntu.

Use Windows10x64.
The device should be defined as "STM Device in DFU Mode"

All I have is Windows 7x64. It does not show in device manager at all.

Looks like CLEAR_MEMORY_DFU has bricked it. :(

I, and not only, used this firmware many times, I did not see anything like it. Try using a different computer if there is a pop-up message when a new device is detected. (close the contacts of the boot, turn on the power, remove the jumper)

Do you have a ST-link V2 programmer?

Making progress. This time, with jumper, Windows installed the driver and it now shows in device manager. I am intentionally not touching anything until I get the next step from you.

I have downloaded DfuSe Demo, but haven't tried to use it. I have been using Ubuntu dfu-util up to this point for everything.

Thanks,
Steve

Install the program, the device should be detected (switch the jumper to boot mode again). Indicate the path to the firmware and flash.

Last firmware 29.09.2019

Sorry to be such a PITA, but at this point I'm nervous about bricking it...

When I select your white.dfu, then press Upload, I get this message box:

Your device was plugged in DFU mode.
So the DFU mode Vid, Pid and Bcd will be put in the .dfu file.
Continue ?

Yes or No ? If No, what's the next step ?

Thanks,
Steve