Month: January 2016

Ericsson and TeliaSonera launches 5G in 2018

Ericsson and TeliaSonera announced that they will test 5G technology in Stockholm, Sweden and Tallinn, Estonia in 2018.

The two companies are vague about exactly what services will be rolled out in the test. This is understandable since the 5G standard is not set yet, and this test is for sure part of defining that standard. But whatever the test includes it will take a lot of engineering efforts to make it happen. Being a digital designer based in the hometown of Ericsson of course I find this highly interesting!

Ericsson has a nice media kit available here with lots of information about 5G.

Earlier both Huawei and Ericsson have announced that they will test 5G technology during the 2018 football world cup in Russia. This is a tougher deadline time-wise; the football world cup will not be postponed. But covering two entire cities with 5G will require a more mature technology.

Ny Teknik and Google blog about gender equality, too!

geek-girl-meetup

Geek Girl Meetup, one of the gender equality champions on GETBlog’s list.

Swedish tech news site Ny Teknik is starting a blog about gender equality in technology. The blog, which has chosen the somewhat unfortunate hashtag #GETBlog, is written by Alice Marshall and is sponsored by Google. According to Google their dream scenario is to copy this initiative to other countries.

The first blog post is a list of the “gender equality champions” in Sweden.

Is this already another sign of change in the industry, like the certifications I wrote about in my previous post? At least I hope that the blog will give me more news and tips about interesting initiatives and people.

You can find the #GETBlog at equality.nyteknik.se.

Coding for sharing – two design rules that will make your colleagues happy

RTL code, or any other code for that matter, is rarely written from scratch. Usually you start your design based on someone else’s code. So to make your code easier to understand for your colleagues or any other person that want to use it, consider these two simple design rules.

Divide your design into structural and functional blocks

A structural block is a block that only contain instances of other blocks and the interconnects between them. A functional block contains logic, registers, memories, and all other neat stuff you want to put in your design.

Most designs have this division naturally. A design is usually a bunch of functional blocks that are connected together in a higher level block.

What is important is to resist the urge to add logic in a structural block, even though this may be the easiest place to fix a bug or change the functionality to match your needs. This is for two reasons:

  • Logic outside a functional block will not be included when the block is copied or re-used in other designs, leading to higher risk of bugs.
  • It is not clear who is responsible for the logic in a structural block.

Use this convention, and no logic will be forgotten or misplaced.

Use special names for I/O signals and interconnects

This naming convention makes it much easier to see the structure of the design for a person that is new to the code.

  • I/O signals get a reserved prefix. For example:
    • Input signals are named i_<signal_name>
    • Output signals are named o_<signal_name>
  • Interconnect signals between blocks are named <driver_instance>_<signal_name>

An example is shown in the picture below.

signal_naming

Signal naming in a structural block. The instance “m” of the module “master” sends a request signal to the instance “s” of the module “slave” and receives an acknowledgment.

If these conventions are used it is always clear whether a port of an instantiated block is an input or an output. The driver of a signal can also be easily seen from the name of the signal. So no more backwards tracing of signals in huge interconnect blocks.

Happy code sharing!

Note: if you use VHDL for coding it is not allowed to read output ports. To get around this problem it is common practice to use an internal signal as an alias for the output port, and then connect the alias signal to the output port. It is a good idea to use special names for these alias signals too, such as a_<signal_name> .

Small steps toward gender equality

I was happy to see that Mycronic got the EDGE (Economic Dividends for Gender Equality) certification recently. Earlier last year Tieto got the same certification.

The uneven gender balance in the electronics industry is a waste of resources and one of many signs that the industry is locked in an old fashioned way of working. If we want to have an even gender balance among electronic engineers equal economic terms is a must. I hope that these types of certifications become industry standard in the future much like the ISO standards for quality control and environmental management.

Read more about the EDGE certification here.

© 2018 Bjurling Logic

Theme by Anders NorenUp ↑