Welcome, Guest. Please login or register.
Did you miss your activation email?
May 14, 2021, 11:10:18 11:10

Login with username, password and session length

Pages: 1 2 3 4 [5] 6 7 8 9 10
 on: May 03, 2021, 07:04:51 07:04 
Started by Johnny - Last post by Johnny
Made a bootloader a few years back that makes your PIC16/PIC18 appear as a mass storage device (flash drive) when plugged into your computer. You can program it by dragging and dropping an intel hex file into the drive or get MPLAB X to automatically transfer to the directory when you press build. Because the bootloader makes use of the USB Mass Storage Class, no software is needed to use the bootloader and it's really fast to upload firmware (feels instant).

Has some other cool features such as viewing your flash memory through a binary file called PROG_MEM.BIN that appears on the drive when user firmware is present. You can also erase the firmware by deleting this file. If your PIC has EEPROM, you can view/modify via an EEPROM.BIN file that will appear on the drive. You can modify your EEPROM by changing values in a hex editor and saving the file, or erase all EEPROM by deleting the file. Some good hex editors are HxD (for Windows), Hex Fiend (for Mac), or Bless Hex Editor (for Linux).

To get into "bootloader mode" you can either insert the USB cable into your computer with the bootloader button held down or reset the PIC whilst the boot button is held. The button can also be used to exit "bootloader mode". A neat trick you can do is get your firmware to detect when the bootloader button is pressed and reset the device. This will start the bootloader because your finger is already on the button when the device resets. So you can toggle between the bootloader and your firmware with the press of a button.

It's fully customisable, but includes hardware profiles for common development boards... Profiles and customisations are done in the config.h (or file, you can choose your bootloader button pin, if you want to use an internal pull-up, active low button, use an LED to indicate you're in the bootloader, crystal options, etc. It's a good idea if you place the button on the MCLRE pin (when MCLRE is disabled of coarse), so you will not lose any useful pins.

There are two versions being developed. One written in C and another version in assembly. The C version requires a PRO license to compile. Currently there is only an assembly version for PIC16F145X. Will port that for PIC18 devices soon.

C version currently supports:

The project code can be found here:
Instructions on how to use the bootloader are on the hackaday page:

Hopefully this is useful to some people.

 on: May 02, 2021, 08:17:15 08:17 
Started by sudni - Last post by bobcat1
Hi ,
Not sure it will work with converted ST-LINK to J-LINK as far as I know the soft in the debugger only work with ST IC ,

But the it might work with General J-Link debugger as this tool is working with al type of ARM controllers

All the best ,


 on: April 30, 2021, 05:27:38 17:27 
Started by sudni - Last post by kreutz
As per:

"The Raspberry Pi RP2040 is fully supported by J-Link. Support was implemented with J-Link Software Pack V6.96.

Note:There seems to be a chip specific issue when trying to reconnect to the target device or if you switch connecttion to the second core. Instead of power cycling this can be solved by connecting Reset (Pin 15) from the J-Link to Pin "RUN" (Chip enable/Reset) of the RP2040."

 on: April 30, 2021, 03:50:35 15:50 
Started by sudni - Last post by h0nk

forget it! v8 hardware will NEVER support RPi Pico processor.

To my best knowledge, the RPi i Pico is an ARM-M0 Architecture.
The debug core should be pretty the same as other M0's.

And even the JLink v8, which mean its Atmel AT91SAM7S based, should be able
to handle ARM M0 in SWD-Mode.

I am not sure, what generation/version a "J-Link Edu Mini" might be.
But i would assume, that it should be able to handle a ARM M0 too.

Can someone explain what goes wrong?

Best Regards

 on: April 30, 2021, 05:57:02 05:57 
Started by sudni - Last post by wild
forget it! v8 hardware will NEVER support RPi Pico processor.

 on: April 29, 2021, 10:37:09 22:37 
Started by max - Last post by pickit2
Lead Acid Batteries are Voltage charged, so why would you want to control from any side?
the main reason they fail is under /or/ over voltage when charging.

 on: April 29, 2021, 09:06:09 21:06 
Started by miskia - Last post by miskia
Thank you for invitation. Registration is done.

Note: This message sent by the system behalf of miskia.

 on: April 29, 2021, 02:03:18 14:03 
Started by kzip - Last post by kzip
CountryUnited Kingdom

 on: April 29, 2021, 11:18:55 11:18 
Started by sudni - Last post by pickit2
seen this on a bookmarked page
Segger have released an updated firmware for their inexpensive J-Link Edu Mini (USD$18)
and their superb Ozone debugger, that allows Raspberry Pi Pico to be debugged like any other J-Link enabled device.

 on: April 29, 2021, 09:51:46 09:51 
Started by sudni - Last post by sudni
Hi all, I use probe Stlink v2 convert in J-link to debug Pico Pi (raspberry Pi pico) and it doesn't work! Embarrassed
Now I am tempted to purchase a Jlink v8 probe for debugging Pico Pi, but I have a doubt. Lips sealed

Is there anyone among you who has already used this probe to debug this card?
Thanks for your help,

Pages: 1 2 3 4 [5] 6 7 8 9 10


... Copyright 2003-2999 ...
Powered by SMF 1.1.18 | SMF © 2006-2009, Simple Machines LLC | HarzeM Dilber MC