Project Introduction: Porting Umon to the Beaglebone Black
ed.sutter at alcatel-lucent.com
Tue May 26 12:34:52 UTC 2015
Thanks for the post. I'm looking forward to this myself..
It has been a while since I've had to do a port totally from scratch
(no reference source code); and since then the chips that were originally
referred to as "microprocessors", then "microcontrollers" and now "SOCs"
have gotten a tad more complex. :-)
As you parse through the uMon code in place now, please don't hesitate to
ask any questions regarding the logic behind some of the design. Be
some of what is there was geared toward an older,
goal that the bootloader would also serve as the debugger and it would
active even after the application takes over.
The code base has been shifting away from that, but many of the hooks and
functional bootup sequence was based on that and may no longer apply.
Anyway, do well on your finals! Really glad I'm not in that space
> Hello all:
> I want to take this time to introduce myself and elaborate the purpose
> for this post. My name is Jarielle Catbagan and I will be working on
> porting Umon to the Beaglebone Black for GSoC 2015 with RTEMS.
> I want to apologize for not posting here recently. I am currently
> running on my last two weeks of classes. Since classes are almost
> done, things are getting a bit hectic; projects due, final
> examinations, etc. Once classes are done, I'll be able to go full
> steam ahead, and when I do I am not stopping. :-)
> Up until now, I was finishing creating the initial posts in my blog
> for the project to give an overview of the project as well as some
> preliminary work that I have done awhile back as a means of proving
> myself. Please feel free to check out my blog at
> http://www.jariellecatbagan.com and let me know what you guys think.
> I'll be using this blog as the main form of documenting my progress
> throughout the project.
> Furthermore, I was setting up my development environment and making
> myself familiar with the Umon sources obtained from the RTEMS repos
> and reading up on the AM335x Technical Reference Manual, AMRv7A
> Architecture Reference Manual, Beaglebone Black System Reference
> Manual, and the MicroMonitor User Manual. I have yet to test and then
> modify the layout of the revised Umon source tree obtained in order to
> build the Umon image.
> I have a repository at https://github.com/jrcatbagan/umon which I will
> be using to track the development of the project. Currently there are
> two branches, 'dev' is where I will be pushing my changes constantly,
> ideally on a daily-basis, and then merging with the master whenever a
> significant milestone has been reached.
> I was and currently am tidying up the source code as I am in the
> process of transforming a copied directory of the csb740 port into
> that of the Beaglebone Black. Step-by-step I am stripping away the
> unnecessary code, including the csb740 specifics and integrating the
> essentials while trying to maximize code reuse as much as possible.
> For the most part, I have been approaching the porting process from
> top-to-bottom. That is, starting from the point where program
> execution first begins and then working form there while modifying the
> implementation to specifically tune it to the Beaglebone Black as I
> traverse the source code. My intention for indicating my approach is
> with the goal of catching any discrepancies. I will be elaborating
> more on this approach as well as what I have done and currently doing
> more extensively very shortly both here and in my blog.
> Finally, to close things up for now up until the next post, I want to
> indicate that I will be working diligently and swiftly to get a Umon
> image with the essential functionalilty up and running on the
> Beaglebone Black before midterm evals.
> umon-devel mailing list
> umon-devel at rtems.org
Alcatel-Lucent Technologies -- Bell Laboratories
Email: ed.sutter at alcatel-lucent.com
More information about the umon-devel