In System Programming Vs In Application Programming

-
Flashing new firmware in the microcontroller can be done in two ways:

1. In System Programming:  The process in which a device can be flashed without removing the chip from the board..

E.g. Flashing the PIC Microcontroller using PICKit

In order to perform ISP operation, the microcontroller is powered up in a special mode: "ISP Mode". ISP mode allows the microcontroller to communicate with an external host device through the serial port such as PC or terminal. Microcontroller receives commands, data over the serial from host, erases and reprograms the code memory.. Once ISP operations has been completed, the device is reconfigured so that it will operate normally the next time it is reset or power removed and reapplied.

Microcontroller by default gets factory shipped by a bootloader. This bootloader will check the state of the pin on boot, and depending on it will either start the user program or will wait for downloading firmware over UART.

2. In Application Programming:  

 Some applications may have a need to erase and program code memory under the control of application. Example: Application may have a need to store calibration information or perhaps need to be able to download new portions of code.

The ability to erase and re-program code memory in the end-user application is "In Application Programming"

Comments

  1. Mateusz Domański15 October 2019 at 10:39

    This comment has been removed by the author.

    ReplyDelete
  2. Mateusz Domański15 October 2019 at 10:42

    When it comes to this type of solutions, unfortunately I do not know about them. From my position I'm satisfied user of IT solutions from https://grapeup.com/cloudboostr/support-and-services/ and I focus mainly on such processes. I know that this is a great solution when it comes to improving our business and managing many issues from the cloud.

    ReplyDelete
  3. Marineworldaquatics24 July 2022 at 03:29

    This blog is very helpful and informative for this particular topic. I appreciate your effort that has been taken to write this blog for us. attack ic chip flash

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more